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

Create/compare new calibrations with updated DAQ firmware

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • None
    • None
    • 4
    • Data Release Production
    • No

    Description

      Build calibrations and compare using the new DAQ firmware version on LATISS that the camera team would like to deploy. The expectation is that it will not have any noticeable effect at the pixel level, but we plan to take a full set of darks+biases+flats with each firmware version on Thursday (08-31) to confirm https://jira.lsstcorp.org/browse/SITCOM-1018.

      Attachments

        1. beeps.jpg
          beeps.jpg
          58 kB
        2. bias_new.png
          bias_new.png
          45 kB
        3. bias_standard.png
          bias_standard.png
          46 kB
        4. dark_new.png
          dark_new.png
          51 kB
        5. dark_standard.png
          dark_standard.png
          52 kB
        6. gain.png
          gain.png
          24 kB
        7. rn.png
          rn.png
          31 kB
        8. verify_daq.log
          10 kB

        Activity

          cslage Craig Lage added a comment -

          Hi czw. jgt and I ran the DAQ test on the AuxTel today (2023-10-03). I took two sets of the standard calibrations, as follows:

          SeqNos 11-203 - New firmware
          SeqNos 209-401 - Standard firmware

          cslage Craig Lage added a comment - Hi czw . jgt and I ran the DAQ test on the AuxTel today (2023-10-03). I took two sets of the standard calibrations, as follows: SeqNos 11-203 - New firmware SeqNos 209-401 - Standard firmware

          I ran both sets of data through the cp_verify code, comparing all exposures to the current set of certified calibrations.  The results seem to match the expectation that there would be no changes to the images.  I've attached comparisons of the gains and read noise determined from the PTC data, along with the list of processing commands.  Verification notebooks are available at the SDF: /sdf/home/c/czw/dev/DM-40595.

          The median gain difference is 0.002, with stddev of 0.003.  Median read noise difference is -0.017 ADU, stddev 0.344 ADU.

          The flat verification is dominated by dust spots/illumination differences.  If there are concerns about the flats, I can generate a combined calibration from one of the firmware sets for verification, but there do not seem to be any other differences.

          The residual ISR-processed bias and dark images look as I would expect, and residual mean plots by amplifier are attached.  These plots add a small x-shift so different amplifiers do not overlap.  C11 and C14 are the two problematic amplifiers in the dark residual plots.  C11 has historically had large scatter (it is the amplifier with the hot column), but C14 was corrected well in the 30s data used to generate the current combined dark.  This likely means an updated dark calibration would be good.

          I've also attached an image of a section of the residual bias image.  There are chains of hot/cold pixels that appear to be imprinted on all amplifiers at the same amplifier-coordinates.  I don't think I've seen this before, and so wanted to report this feature.  These chains are visible in both the bias and the dark, and with both sets of firmware.  They do not repeat in the same location on different exposures, but all of the images I looked at had at least one chain per amplifier.  The signal seems to be at most +/- 50 ADU, with a rough by-eye sigma ~ 25 ADU.

          Let me know if anyone would like more analysis, but as mentioned above, the firmware change seems to have no effect on the images produced by LATISS.

          czw Christopher Waters added a comment - I ran both sets of data through the cp_verify code, comparing all exposures to the current set of certified calibrations.  The results seem to match the expectation that there would be no changes to the images.  I've attached comparisons of the gains and read noise determined from the PTC data, along with the list of processing commands.  Verification notebooks are available at the SDF: /sdf/home/c/czw/dev/ DM-40595 . The median gain difference is 0.002, with stddev of 0.003.  Median read noise difference is -0.017 ADU, stddev 0.344 ADU. The flat verification is dominated by dust spots/illumination differences.  If there are concerns about the flats, I can generate a combined calibration from one of the firmware sets for verification, but there do not seem to be any other differences. The residual ISR-processed bias and dark images look as I would expect, and residual mean plots by amplifier are attached.  These plots add a small x-shift so different amplifiers do not overlap.  C11 and C14 are the two problematic amplifiers in the dark residual plots.  C11 has historically had large scatter (it is the amplifier with the hot column), but C14 was corrected well in the 30s data used to generate the current combined dark.  This likely means an updated dark calibration would be good. I've also attached an image of a section of the residual bias image.  There are chains of hot/cold pixels that appear to be imprinted on all amplifiers at the same amplifier-coordinates.  I don't think I've seen this before, and so wanted to report this feature.  These chains are visible in both the bias and the dark, and with both sets of firmware.  They do not repeat in the same location on different exposures, but all of the images I looked at had at least one chain per amplifier.  The signal seems to be at most +/- 50 ADU, with a rough by-eye sigma ~ 25 ADU. Let me know if anyone would like more analysis, but as mentioned above, the firmware change seems to have no effect on the images produced by LATISS.

          People

            czw Christopher Waters
            erykoff Eli Rykoff
            Christopher Waters, Craig Lage, Eli Rykoff, Erik Dennihy
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Jenkins

                No builds found.