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

dcrAssembleCoadd makes too many nImages

    Details

    • Templates:
    • Story Points:
      1
    • Team:
      Alert Production

      Description

      The option doNImage is very handy for coadd assembly, as it creates an "nImage" of each patch with pixel values that show how many images (i.e., warps) will be assembled at that location. The nImages are saved as fits files. However, things get a little complicated with dcrAssembleCoadd's nImages.

      This ticket is to change the present situation so only one nImage is created one time. The current state of affairs with doNImage (approximately in order):

      • dcrAssembleCoadd calls regular assembleCoadd, which creates an nImage for all patches in the deepCoadd directory before beginning assembly
      • These nImages are overwritten with nImages that have pixel values 3x larger than before (in this example, 3 is the number of DCR subfilters being used)
      • Another set of nImages is created in the dcrCoadd directory alongside the dcr coadds, which are identical to the original nImages

      Somewhat related to this, when one uses the butler to load a DCR coadd and does dcrCoadd.getInfo().getCoaddInputs().visits, it lists each constituent visit 3 times (i.e., nSubfilter times). This is probably also a bug.

        Attachments

          Container Issues

            Activity

              People

              • Assignee:
                sullivan Ian Sullivan
                Reporter:
                mrawls Meredith Rawls
                Reviewers:
                Meredith Rawls
                Watchers:
                Ian Sullivan, Meredith Rawls
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel