Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses https://github.com/DiamondLightSource/mx-analysis/issues/50
Adds function to trigger service for running multi-xia2. On most MX beamlines, mutli-xia2 runs automatically on data collections collected in the same data collection group. This used to also be true for I23. I23 no longer have data collection group functionality (not clear why this the case), however, they would still like multi-xia2 to run on MAD wedge style experiments.
The new trigger function is designed to be called with a delay from the start of the xia2 recipes. The trigger function has logic to then check to see if any more recent data collections have been made with matching sampleid, sessionid, prefix and run number. If there is a more recent collection, the trigger is skipped as the more recent data collection will also attempt to trigger multi-xia2. If there is not a more recent data collection that matches the criteria, the MAD wedge experiment will have been assumed to have completed and the pipeline will run. The delay (which is set by the recipe) should be long enough to allow subsequent wedges to have been collected before the trigger conditions are assessed.