Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-11356

Confusion of refObjLoader.pixelMargin and matcher.maxOffsetPix

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: meas_astrom
    • Labels:
      None
    • Templates:
    • Team:
      External

      Description

      A recent change in AstrometryTask.solve increases the exposure bounding box by the matcher's maximum offset (matcher.maxOffsetPix. However, a parameter already exists to provide this growth in the reference catalog loader (refObjLoader.pixelMargin). Because the exposure bounding box is increased artificially after recording the catalog loading radius, loading the normalised persisted matches results in many missed matches.

      To fix this:

      • Remove the additional grow
      • Set the default refObjLoader.pixelMargin to match the default matcher.maxOffsetPix.
      • Add notes advising the user that the two parameters should be linked.
      • Stop AstrometryTask from reaching into the responsibility of the reference catalog loader (it shouldn't need to know about the details of the refObjLoader configuration).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                price Paul Price
                Reporter:
                price Paul Price
                Reviewers:
                Chris Morrison
                Watchers:
                Chris Morrison, Hsin-Fang Chiang, John Swinbank, Paul Price, Scott Daniel, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel