Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_algorithms
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:AP F18-6, AP S19-1, AP S19-2, AP S19-3
-
Team:Alert Production
Description
The various camFlux fields in the existing reference catalogs are unused and their purpose is unclear (especially now that we have color term maps). We should remove them entirely from meas_algorithms.
Attachments
Issue Links
- is triggered by
-
RFC-535 Make flux error a required field in reference catalogs
- Implemented
Switching this back to `ToDo`. Per my initial work, and a conversation with Simon Krughoff, Russell Owen and Jim Bosch, it seems that everyone's assumptions about camFlux not being necessary were unfounded. LoadReferenceObjectsTask._addFluxAliases() uses the filterMap to create camFlux_X->flux_Y aliases that are used by getRefFluxField to determine the closest flux field to a given filter for that camera. This approach is rather non-obvious (as evidenced by the people who wrote it being confused by it) and makes it very clumsy to create refcats for testing purposes, but we were not able to come up with an obviously better solution.
We may want to wait for gen2 butler to go away and then RFC a full rethink of how filterMaps are handled.