Closed jeanconn closed 5 years ago
Going OT, at some point in the not-too-distant future you should process a couple of SRDCs and see if this value persists. Most likely not since it arises from a large value in im1.fits in 2019:002 and is not in im2.fits. My recollection is that the 5-sec read generally occurs before the 10 sec, so it is hard to imagine this is real. Nevertheless...
It is fair to just clip at 0.0. I'm almost inclined to put that upstream in mica dark_cal as a default value for clipping (with the option to set to None for no clipping).
But in any case clipping to 0 in proseco is just fine. The real dark current cannot be negative.
"My recollection is that the 5-sec read generally occurs before the 10 sec, so it is hard to imagine this is real. Nevertheless..." I just couldn't wrap my mind around the pixel having a large value in the 5 second readout and a small value in 10 second readout for each replica.
And I had the SRDC thought as well when we were wondering about the star selection, but we'll get there eventually.
Closed by mica 3.16 .
For star selection and review how should a pixel with a reported value like the -8570 below be handled? Is it a bad/broken pixel that should just be completely avoided for guide stars and fids? Or should it just be set to 0 so it doesn't cause numeric issues?