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

Debug and fix source ID failures in Gen3 ForcedPhotCoadd discovered in Gen3 RC2

    XMLWordPrintable

    Details

    • Team:
      Data Release Production
    • Urgent?:
      No

      Description

      See the last few comments on DM-29528. Something is going wrong in either MergeMeasurements or ForcedPhotCoadd that's resulting in some kind of source ID inconsistency.

        Attachments

          Issue Links

          duplicates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-29907 Fix meas_extensions_scarlet sorting issue

          • Done
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-29528 Gen3 RC2 processing with w_2021_14 stack

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-29737 Check if a SourceCatalog is sorted when calling `find`

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            jbosch Jim Bosch added a comment -

            DM-29737 should fix this, but I'm going to keep this open until I have a chance to understand why the catalogs aren't sorted (see https://lsstc.slack.com/archives/C2JPMCF5X/p1618428539388800), as fixing that is worthwhile too - it will address the (probably tiny) performance regression the DM-29737 fix along would imply, and if we don't see this problem in Gen2 (as seems to be the case as per https://lsstc.slack.com/archives/C2JPMCF5X/p1618448136422900?thread_ts=1618428676.389500&cid=C2JPMCF5X), I bet tracking it down will help with Gen2<->Gen3 parity.

            Show
            jbosch Jim Bosch added a comment - DM-29737 should fix this, but I'm going to keep this open until I have a chance to understand why the catalogs aren't sorted (see https://lsstc.slack.com/archives/C2JPMCF5X/p1618428539388800 ), as fixing that is worthwhile too - it will address the (probably tiny) performance regression the DM-29737 fix along would imply, and if we don't see this problem in Gen2 (as seems to be the case as per https://lsstc.slack.com/archives/C2JPMCF5X/p1618448136422900?thread_ts=1618428676.389500&cid=C2JPMCF5X ), I bet tracking it down will help with Gen2<->Gen3 parity.
            Hide
            Permalink
            jbosch Jim Bosch added a comment - - edited

            This problem has turned out to be more than just DM-29737 could fix, but further work and discussion has moved to DM-29907, so I'm closing this as a duplicate.

            Show
            jbosch Jim Bosch added a comment - - edited This problem has turned out to be more than just DM-29737 could fix, but further work and discussion has moved to DM-29907 , so I'm closing this as a duplicate.

              People

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

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.