DM-12549: ap_pipe must call AssociationTask in a reproducible order #121
Conversation
This file contains 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
Association will now be run in ascending visit ID order, ensuring consistent results between runs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR enforces the running of source association (or, more precisely,
DiaPipelineTask) in Gen 3 in order of increasing visit ID. Association may still be run in parallel for different detectors within the same visit, and other tasks should be unaffected.This PR makes no attempt to constrain the Gen 2 processing order, as the tooling needed to do so is completely different.
Depends on lsst/ctrl_mpexec#118.