Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Labels:
-
Story Points:3
-
Epic Link:
-
Sprint:AP S21-4 (March)
-
Team:Alert Production
-
Urgent?:No
Description
In order to let ap_verify produce reproducible results, ap.pipe.doAssociation must always submit visits to the association database in the same order. The specific order should not matter in terms of the scientific validity of the associations (Chris Morrison [X], priv. comm.), so it can be chosen to optimize the code.
Note that this ticket is meaningless until DM-11372 or DM-12314 is resolved, since currently the order in which visits are handled must be externally imposed (see DM-12535).
Attachments
Issue Links
- is blocked by
-
DM-29345 Add method to get QuantumNodes by TaskDef
- Done
-
DM-13163 Refactor ap_pipe to use CmdLineTask primitives
- Done
-
DM-11372 Create CommandLineTask utility in `ap_pipe`
- Won't Fix
-
DM-12314 Generalize ap_pipe to multiple visits
- Invalid
- is triggering
-
DM-24370 Support extensible scheduling in pipetask
- Done
- relates to
-
DM-18684 Ensure DIAObject association records sufficient temporal information for reproducability
- To Do
-
DM-21916 SQuaSH upload of Gen 3 Measurements
- Done
-
DM-21939 Create Gen 3 AP Pipeline
- Done
-
DM-29113 Create Gen 2 vs. Gen 3 comparison dashboard
- Done
-
DM-12535 Wrap ap_verify and run it over HITS dataset
- Done
- mentioned in
-
Page Loading...
I assume "visit" was being used broadly in the sense of "observation", and that a nondeterministic CCD order will still give minor catalog changes?