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

Decide how to handle erroneous error propagation noted in DM-19828

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: meas_mosaic
    • Labels:
      None
    • Team:
      Data Release Production

      Description

      In DM-19828, it was noted that:

      "something is amiss with the implementation and/or application of the photoCalib as persisted by meas_mosaic. In applying it to calibrate a catalog, the fluxes seem to come out ok, but the S/N distributions are completely messed up, so it is the fluxErr's that are getting computed erroneously."

      This ticket is to follow-up on the issue: either by fixing the the root cause of the issue or by removing the photoCalib persistence from meas_mosaic altogether. The former may be preferred if only to ensure this is not a red herring pointing to a fundamental issue with a certain use flavour/pattern for/with photoCalib persistence/application that should be addressed so that potential future users do not hit it. The latter is less satisfactory, but may be acceptable in that the only code that makes use of the meas_mosaic-persisted photoCalib are the scripts in pipe_analysis (and they can be reverted to use the original ubercal datasets persisted by meas_mosaic).

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                jbosch Jim Bosch
                Reporter:
                lauren Lauren MacArthur
                Watchers:
                Lauren MacArthur
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel