-
Notifications
You must be signed in to change notification settings - Fork 2
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
Screen and collect screens but subsequent collections are not made #703
Comments
Raised gerrit https://gerrit.diamond.ac.uk/c/gda/gda-mx/+/43072 |
I've +1'd the gerrit change, although the build failed because of an 'Unknown Error'. Also, this seems like one we should test on the beamline before putting the GDA change on live, so let's leave this issue open until it's tested |
As seen in #769, there was also an issue where we weren't passing To confirm fix:
|
Closing this as it has been clearly working on the beamline for a while now. Can re-open if there's a new issue |
Discovered during testing in #697
Screen and collect is screening, but not collecting, the request never gets as far as hyperion.
See e.g. https://ispyb.diamond.ac.uk/dc/visit/mx23694-123/id/16086403
which is the screening collection, but the full collection was not then performed
after performing the screening collection, gda then logs:
And then immediately moves on to the next sample
Suspect this is because self.sampleProvider.setSample(sample) in robot_load_and_centre/hyperion.py is never called when using load_centre_collect - the sampleProvider sample is then ultimately used by UDCRunner to fetch the next instruction but this is always null because it is never set.
Acceptance Criteria
load_centre_collect_full
plan is used in hyperionThe text was updated successfully, but these errors were encountered: