Closed araichoor closed 2 months ago
I am re-QA’ing the 20240730-20240805 nights that have been re-processed with the new r1 cte fix. I have just checked 20240730 so far. it looks good, especially in terms of redshifts and lya (individual tiles plot, overall per-petal diagnoses).
though I notice a small feature in the sframesky, at the bluest pixel: see the white pattern at the very left (over the “1” in red):
and I also see some excess of z~0.5 in the skyzfiber plot. to make it more visible, I compile here all the redshifts of the sky fibers for maindark tiles with efftime > 850s since 20240730:
I suspect that:
I ll just wait until tomorrow to allow anyone to chime in (@julienguy, @schlafly ?), in case this deserves more investigation.
The "small feature in the sframesky at the very blue wavelengths" is caused by a negative sky model in that region. I see the step in the sky flux as a function of fiber number from the CTE correction at the expected fiber ids from the defined OFFCOLSA: '450:1184,1184:2056' calibration param, but I am surprised that the amplitude of the steps is much larger at 5764A than at 6080A or 6880A.
Sky model flux as a function of fiber number for some wavelengths (from the file /global/cfs/cdirs/desi/spectro/redux/daily/exposures/20240730/00246358/sky-r1-00246358.fits.gz
)
The variation of the offset was caused by the flat field correction applied to the sky model, that also corrects for variations from spectrograph to spectrograph and can have large variations at the shortest or largest wavelength because of the dichroics.
So the problem here simply a limitation of the OFFSET correction that is constant across wavelength: it fails when the sky level becomes lower than the correction to apply, which happens at the shortest wavelengths because of the dichroic.
Thanks Anand. I don't think we have good alternatives to this CTE correction at present, and if there aren't major impacts on the redshifts, let's move forward with it. i.e., please mark as good, thank you!
thanks both for the investigation + feedback. I ll continue QA'ing those, and validate if nothing else shows up.
ok, I ve QA-validated tiles from 20240730, 20240801, 20240802, 20240803, and 20240805 (https://desi.lbl.gov/trac/changeset/3985/data). I ve moved all their status from “unsure” to “valid”. there were 65 tiles (bright=16, dark=49).
closing the ticket.
opening a ticket for the record (sorry I forgot to do that):
20240730 - 20240805 nights have been reprocessed on Aug. 12. I am going to re-QA those.