Details
-
Type:
Story
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: meas_astrom
-
Labels:
-
Story Points:6
-
Epic Link:
-
Team:Alert Production
Description
Currently the catalog of reference objects in the matcher is not loaded on a area relative to the max shift/rotation allowed. For larger shifts/rotations/distortions this could lead to portions of the chip being outside of the loaded reference catalog area and thus unconstrained in future wcs fitting.
Deliverables: Fix to meas_astrom so that it loads an area of the reference catalog relative to the max shift/rotation.
Attachments
Activity
I agree with Paul Price; the reference object loader already grows the region by some amount to help with this (as per Paul's suggestion). I don't think it's directly tied to the maximum shift distance though---I vaguely remember it being a fixed size in pixels? It might make more sense to just update that logic.
Colin Slater
added a comment - I agree with Paul Price ; the reference object loader already grows the region by some amount to help with this (as per Paul's suggestion). I don't think it's directly tied to the maximum shift distance though---I vaguely remember it being a fixed size in pixels? It might make more sense to just update that logic. Okay I'll change the title and description.
Found how to add a static padding to the bounding box used to load the reference catalog. Need to tie this padding amount to the maximum allowed shift in the matcher.
The work of this ticket was completed inside of DM-9750.
Instead of adding more I/O, we should load the catalog once only with an additional buffer in the search radius, where the buffer is equal to the maximum possible offset.