Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: fgcmcal
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:DRP S20-3 (Feb)
-
Team:Data Release Production
-
Urgent?:No
Description
The configuration format for FgcmFitCycleTask has some elements that must be specified in band order. While this was fine (such as it was) with 5 bands (g,r,i,z,y), with the addition of several narrow-bands this has become more obviously unwieldy. It would be easy to change these configs to use dictionary mappings instead of ordered lists which would remove ambiguity and make mis-configurations much less likely.
Some comments on the PRs, but looks good to me (although, admittedly, I’m relying somewhat on your personal testing...). A green Jenkins & you’re good to go.