Looking at 18a filter scan data, I noticed ALL the data frames (single destructive reads) have some funny behavior. In the plot, the white dots are the first row of 1024 pixels, the green are row 510 (but are generally true for rows 1 to 1022), and the red dots are the last row of 1024 pixels.
You can't really see it from this plot, but the first row clearly shows the 4 readout chains while the others don't show that imprint clearly.
The first row, after 4 reference pixels near 15,000 ADU, jump to 16,000 ADU and slowly climb to 16,200 before a short jump down to the last 4 reference pixels.
The middle rows look like like good data with a sharp jump on the end 4 reference pixels the only big weirdness. It is a little weird to me that reference pixels at start have more charge than data.
The last row almost seems pinned at a saturation value (3200 ADU). First four reference pixels are all around 14,500 ADU and last four reference pixels are 10,500; 10,500; 10,500; 2500 ADU.
Don't know if this is partially coming from ebox interacting with array, but something looks screwy.

No comments:
Post a Comment