Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler
-
Labels:
-
Story Points:12
-
Epic Link:
-
Sprint:BG3_F18_08, BG3_F18_09, BG3_F18_10
-
Team:Data Release Production
Description
The Gen2->Gen3 converter code (daf.butler.gen2convert) currently ignores calibration repos. We want to add each Gen2 Calib repo as a new Collection in Gen3. The tricky part will be converting from the date-range lookup in the Gen2 calibration registries to the ExposureRanges (integer IDs) used by Gen3.
Attachments
Issue Links
- is parent task of
-
DM-16065 ci_hsc does not validate calibration data in converted gen3 repository
- Invalid
Activity
Yes, this is in progress. Sorry for not marking it as so; I'm still getting used to the tracking side of development.
Some comments on the daf_butler PR, but overall looks good!
Since I don't see a ci_hsc branch, I assume the state of testing is that ci_hsc automatically runs this new code, but there is no verification there that the calibration Datasets are appearing in the gen3.sqlite3 there. Have you done a one-off test of that? How hard would it be to automate it?
I have been running independent validation, but had not looked into the validation code in ci_hsc until today. I'm unclear on how the dataId is being set, and may push and merge my current changes and add a ticket to fix the validation in ci_hsc independently.
Complete, although I will need to finish automatic validation of the gen3 calibration products (DM-16065).
Christopher Waters, this is indeed in progress, right? (I just want to get Jira reflecting reality.)