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

Possible masking issue in ip_isr

    XMLWordPrintable

Details

    • Bug
    • Status: Invalid
    • Resolution: Done
    • None
    • ip_isr
    • None
    • Data Release Production
    • No

    Description

      mfisherlevine reported today that the RubinTV processing was claiming N>0 pixels were marked as BAD, despite that processing not applying defects (or much other ISR steps beyond overscan).  When I ran the example attached on the RSP, I found a similar result, with lsst.isr INFO: Set 9598 BAD pixels to 245.000000. appearing in the log.

      Running the same code in the terminal with a pdb breakpoint resulted in no masked pixels, even when I switched versions from the w.2023.16 build to the older version running at the RSP (g8db5811388+2736d543e7 from mid-February it seems).  Without defects, I think the only code that sets BAD masks is in updateVariance, which sets that when the image is negative (which shouldn't be the case with this minimal ISR processing).

      Attachments

        Activity

          No work has yet been logged on this issue.

          People

            Unassigned Unassigned
            czw Christopher Waters
            Christopher Waters, Eli Rykoff, Merlin Fisher-Levine
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Jenkins

                No builds found.