Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:AP S22-5 (April)
-
Team:Alert Production
-
Urgent?:No
Description
Krzysztof Findeisen reported that my merge of DM-27013 broke the ap_verify runs for at least DECam, and possibly HSC. I've verified this in my own run (see below). This should be a simple fix to the pipeline config.
File "/home/parejkoj/lsst/lsstsw/stack/lsst-scipipe-3.0.0/Linux64/meas_algorithms/gf36ae6ace1+09a7694010/python/lsst/meas/algorithms/loadReferenceObjects.py", line 228, in validate
|
raise pexConfig.FieldValidationError(LoadReferenceObjectsConfig.anyFilterMapsToThis,
|
lsst.pex.config.config.FieldValidationError: Field 'astromRefObjLoader.anyFilterMapsToThis' failed validation: `filterMap` and `anyFilterMapsToThis` are mutually exclusive
|
For more information see the Field definition at:
|
File meas/algorithms/loadReferenceObjects.py:199 (LoadReferenceObjectsConfig) and the Config definition at:
|
File meas/algorithms/loadIndexedReferenceObjects.py:34 (<module>)
|
Attachments
Issue Links
- is triggered by
-
DM-27013 Change CalibrateTask refcat defaults to Gaia DR2 for astrometry and PS1 for photometry
- Done
It's both DECam and HSC. All three datasets use filterMap to spell out the filters used by the dataset's built-in refcats; I think they predate anyFilterMapsToThis entirely.