Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_astrom
-
Labels:
-
Story Points:5
-
Epic Link:
-
Sprint:DRP S21b
-
Team:Data Release Production
-
Urgent?:No
Description
While looking for some "pretty picture" for the DP0.1 data, Jeffrey Carlin noticed some "green, point-like sources that are slightly offset from galaxies in this DC2 (gri-bands) images". In a 'lengthy" discussion on this slack thread (108 replies and counting!), James Chiang narrowed it down to a bad WCS for detector 64 of the r-band visit 908967 (whereas surrounding fits looked ok).
It was noted that, upon a new processing of the exposure, the "badness" of this fit was revealed in the scatter output from the astrometry task to the logs:
calibrate.astrometry INFO: Matched and fit WCS in 3 iterations; found 54 matches with scatter = 0.317 +- 0.193 arcsec |
whereas, e.g., the neighboring detector 65 has a more "typical" scatter of:
calibrate.astrometry INFO: Matched and fit WCS in 3 iterations; found 81 matches with scatter = 0.006 +- 0.003 arcsec |
It was also noted that this bad fit was actually flagged by running checkCchAstrometry.py during the processing, but apparently these flagged detectors were not omitted from from the coadd assembly. Johann Cohen-Tanugi has provided a full list of such bad fits from the DP0.1 run, attached here.
Look into what is going wrong with these WCS fits, starting with a deeper dive on detector 64 of visit 908967.
Attachments
Issue Links
- relates to
-
DM-30657 Add ability for magLimit in reference source selection to be based on band of dataset
- To Do
-
DM-30943 Turn on delta mag rejection for astrometry matching in configs for LSSTCam-imSim
- Done
-
DM-32129 Add a maximum mean offset threshold for SFM astrometry fit success
- Done
-
DM-16301 Integrate DESC's checkCcdAstrometry into ProcessCcd itself
- Won't Fix
Johann Cohen-Tanugi, let me know if you'd like to see any further validations on this ticket. I have created DM-30657 to add the doPerBandRefMagLim reference culling I've been using above (the option will be defaulted to False, so to make use of it a specific and deliberate config override in any given obs package will be required). I may also explore a more dynamic culling based on the icSrc detection limits (but perhaps not on the short term). And, more importantly, Eli is working on the real fix to this vulnerability on
DM-30490.