-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a basic datacollection simulator #163
Conversation
This should be good to go now |
@abstractmethod | ||
def run(self, *args, **kwargs): | ||
pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need an abstract class for something that only has a single implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is that in future you might want to simulate something other than a data collection. There are plenty of things populated by the acquisition client that are not handled by ispyb-api. For example a RobotAction is not a DataCollection, nor is an XFEFluoresenceSpectrum. Would need a bit of tinkering on the arg parser to select the relevant class but should be flexible enough
Try again... |
Ping |
Without any further feedback im gonna merge this |
Not as full featured as dc_sim but lets folk outside of dls simulate a data collection and trigger mimas.