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

Cannot do linearity corrections in Gen 3 DECam processing

    Details

    • Team:
      Data Release Production
    • Urgent?:
      No

      Description

      IsrTask has code to construct a linearizer (ip.isr.linearize.LinearizeBase) from Butler datasets. However, this code cannot be used at present in Gen 3 because:

      • IsrTask does not have a PrerequisiteInput for linearizer data
      • it is not clear where this data should come from in a new DECam repository. See discussions on #dm-middleware on March 16 and March 23. (In Gen 2, the linearizer is a virtual dataset handled by the CameraMapper, but everybody agrees that in Gen 3 it should be stored in the repository proper.)

      Please provide a way to make the linearizer data available in Gen 3 DECam repositories, both in from-scratch repositories (see DM-21862) and in repositories converted from Gen 2.

        Attachments

          Issue Links

            Activity

            krzys Krzysztof Findeisen created issue -
            krzys Krzysztof Findeisen made changes -
            Field Original Value New Value
            Link This issue relates to DM-23616 [ DM-23616 ]
            krzys Krzysztof Findeisen made changes -
            Link This issue is blocked by DM-23044 [ DM-23044 ]
            krzys Krzysztof Findeisen made changes -
            Description {{IsrTask}} has code to construct a linearizer ({{ip.isr.linearize.LinearizeBase}}) from Butler datasets. However, this code cannot be used at present in Gen 3 because:
            * {{IsrTask}} does not have a {{PrerequisiteInput}} for linearizer data
            * it is not clear where this data should come from in a new DECam repository. See discussions on {{#dm-middleware}} on [March 16|https://lsstc.slack.com/archives/C2JPT1KB7/p1584401758440300] and [March 23|https://lsstc.slack.com/archives/C2JPT1KB7/p1584988801115600]. (In Gen 2, the linearizer is a virtual dataset handled by the {{CameraMapper}}, but everybody agrees that in Gen 3 it should be stored in the repository proper.)

            Please provide a way to make the linearizer data available in Gen 3 DECam repositories, both in from-scratch repositories (see DM-21862) and in repositories converted from Gen 2.
            {{IsrTask}} has code to construct a linearizer ({{ip.isr.linearize.LinearizeBase}}) from Butler datasets. However, this code cannot be used at present in Gen 3 because:
            * {{IsrTask}} does not have a {{PrerequisiteInput}} for linearizer data
            * it is not clear where this data should come from in a new DECam repository. See discussions on {{#dm-middleware}} on [March 16|https://lsstc.slack.com/archives/C2JPT1KB7/p1584401758440300] and [March 23|https://lsstc.slack.com/archives/C2JPT1KB7/p1584988007111300]. (In Gen 2, the linearizer is a virtual dataset handled by the {{CameraMapper}}, but everybody agrees that in Gen 3 it should be stored in the repository proper.)

            Please provide a way to make the linearizer data available in Gen 3 DECam repositories, both in from-scratch repositories (see DM-21862) and in repositories converted from Gen 2.
            krzys Krzysztof Findeisen made changes -
            Labels gen3-middleware gen2-deprecation-blocker gen3-middleware
            czw Christopher Waters made changes -
            Link This issue relates to DM-23044 [ DM-23044 ]
            krzys Krzysztof Findeisen made changes -
            Link This issue blocks DM-21888 [ DM-21888 ]
            czw Christopher Waters made changes -
            Link This issue is blocked by DM-24703 [ DM-24703 ]
            gruendl Robert Gruendl made changes -
            Remote Link This issue links to "Page (Confluence)" [ 25785 ]
            Hide
            tjenness Tim Jenness added a comment -

            Christopher Waters do I understand from the related tickets that this ticket is now unblocked and that we just need to put a serialized linearizer yaml file for DECam into obs_decam_data?

            Show
            tjenness Tim Jenness added a comment - Christopher Waters do I understand from the related tickets that this ticket is now unblocked and that we just need to put a serialized linearizer yaml file for DECam into obs_decam_data?
            Hide
            czw Christopher Waters added a comment -

            I believe so.  I didn't do so as a part of DM-24703 as the gen2 behavior was unchanged, and knew that this ticket existed for checking the gen3 behavior.

            Show
            czw Christopher Waters added a comment - I believe so.  I didn't do so as a part of DM-24703 as the gen2 behavior was unchanged, and knew that this ticket existed for checking the gen3 behavior.

              People

              • Assignee:
                Unassigned
                Reporter:
                krzys Krzysztof Findeisen
                Watchers:
                Christopher Waters, Dino Bektesevic, John Swinbank, Krzysztof Findeisen, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel