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

Investigate failed detector-visit in DC2 4 patch run

    XMLWordPrintable

Details

    • Story
    • Status: To Do
    • Resolution: Unresolved
    • None
    • None
    • None
    • 2
    • AP F22-1 (June)
    • Alert Production
    • No

    Description

      In the DC2 run that Meredith made in DM-34828, we had one failure: {{{instrument: 'L
      SSTCam-imSim', detector: 36, visit: 1185194}}, which failed astrometry running with the latest weekly (w_2022_22), but passed in the previous weekly (w_2022_21), with a catastrophically bad fit:

      Exception TaskError: Fatal astrometry failure detected: mean on-sky distance = 8.994 arcsec > 0.050 (maxMeanDistanceArcsec)
      

      This is simulated data, so there's no obvious reason that it should have failed. The new weekly includes my plugin removal from the config, but likely also includes many other changes as DRP was pushing for things to be included in this weekly for HSC.

      We should look at the input images (icExp) and catalogs (icSrc) to calibrateTask in reach of those runs to try to figure out what might have gone wrong.

      See the full log here: /project/mrawls/ap_profile/submit/u/mrawls/DM-34828-w_2022_22/20220526T202214Z/jobs/calibrate/1185194/6d50eec5-36fc-49f1-a9c2-4f5d2ac1636a_calibrate_1185194_36.3906983.err

      Attachments

        Issue Links

          Activity

            sullivan Ian Sullivan added a comment -

            ctslater bringing this ticket to your attention, in case this failure is relevant to your V&V work with DP0.2

            sullivan Ian Sullivan added a comment - ctslater bringing this ticket to your attention, in case this failure is relevant to your V&V work with DP0.2
            ctslater Colin Slater added a comment -

            This is a manifestation of DM-32129 and tickets linked from there. The root cause is that the DC2 reference catalog is overly deep and can trigger false matches. It is somewhat surprising that it changes between weeklies.

            For reference, here are other collected error messages from DP0.2: https://confluence.lsstcorp.org/display/LSSTOps/DP0.2+Error+Categorization

            ctslater Colin Slater added a comment - This is a manifestation of DM-32129 and tickets linked from there. The root cause is that the DC2 reference catalog is overly deep and can trigger false matches. It is somewhat surprising that it changes between weeklies. For reference, here are other collected error messages from DP0.2: https://confluence.lsstcorp.org/display/LSSTOps/DP0.2+Error+Categorization

            People

              mrawls Meredith Rawls
              Parejkoj John Parejko
              Colin Slater, Eric Bellm, Ian Sullivan, John Parejko, Meredith Rawls
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Jenkins

                  No builds found.