Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ci_hsc, ci_hsc_gen3
-
Labels:
-
Story Points:7
-
Epic Link:
-
Sprint:DRP S21a (Dec Jan)
-
Team:Data Release Production
-
Urgent?:No
Description
As part of the acceptance criteria towards deprecating the "gen2" middleware in favor of the almost-ready-for-prime-time "gen3" middleware, detailed consistency checks between the data products produced by each must be made. This may not require bitwise-esque identity in all cases, but any differences should be understood and deemed acceptable/preferable on the gen3 side of things. As a first step, on this ticket, processing outputs will be assessed up to and including the Single Frame Processing stage using the outputs of the two HSC continuous integration packages (ci_hsc_gen2 vs. ci_hsc_gen3), which probe a limited dataset (in testdata_ci_hsc), but provide a nice starting point for these comparisons. In particular, the outputs created by ci_hsc_gen2 include a conversion of its gen2 repo into a gen3 one. This may ease certain types of comparisons (and could provide another sanity check on the middleware flavor conversion scripts).
This ticket is a precursor to a more complete and thorough consistency check to be done on DM-21872.
Attachments
Issue Links
- relates to
-
DM-28936 Try to get calibration source selection consistent between gen2 and gen3 middleware
- Done
-
DM-29819 Compare the data products of the gen2 vs. gen3 w_2021_14 RC2 runs up to Single Frame Processing
- Done
-
DM-21872 Final middleware consistency check for DRP pipelines
- Invalid
-
DM-28806 Transfer validation checks from ci_hsc_gen2 to ci_hsc_gen3
- Invalid
Note to self: Keep
DM-28806in mind while becoming more familiar with the structure and execution of these scripts.