Christopher Waters added a comment - 21/Apr/23 9:51 PM I'm adding a notebook with the results of a selection of biases, along with the individual plots so I can share on slack as well.  To check these results, I ran a set of three biases from each of the days listed in Chris Stubb's plots through the cp_verify code as a proxy for the full-bias construction results.  This will use the appropriate bias from the butler. I've plotted the profiles from the cpVerifyProc images (bias frames that have had only overscan and bias corrections applied) for both rows and columns 500 and 2500 (full size available in attachments).  The row profiles (left panels) show a similar pattern as those above, and the column profiles (right panels) show the midline break (exposures sorted such that dateobs increases in the -y direction): There's a change in the pattern that corresponds to the updated sequencer file, also plotted as a function of exposure in the -SEQ.png image.  This also corresponds with the construction of calibrations with the parallel overscan enabled.  The existence of the patterns indicates that while new data is being treated correctly with parallel overscan, the older data is still using a previous bias that is "re-printing" the pattern back into the images.  I've filed  DM-38828 to fix that. I've also attached a plot of the difference in measured and nominal read noise (which comes from the detector object), as the verification notebook (also attached) indicates that all amplifiers are failing the NOISE test, such that the measured noises are more than 5% different than the nominal values.  The plots show that the measured read noises are smaller than the nominal values, which I thought was no longer flagged as a failure.