Subject: Re: Re: 2.5m obslog 000126 (MJD 51570)
Date: Thu, 27 Jan 2000 18:39:18 -0600
From: Ronald Rechenmacher
skent@fnal.gov said:
> Ron,
> These errors have been around for a long time and while Connie
> understands them much better than I, they seem to not have any impact
> on the data quality.  Provided they occur only occassionally, I am
> guessing that they only affect an odd pixel here or there in the
> overscan regions, and one is normally medianing pixel values there
> anyway, so they are of no conequence.  Is there anyway to determine
> which row of which frame of which CCD the error occurs?  One could
> look at the raw frames to see if there is any visible artifact.
The DA currently does not output the row information... it gets lost.
It would be trivial to add another output line with the row info.
The ccd info is included in the message and the frame info is output
separately into the log such that the frame info could easily be associated
with a "WRONG PIX" message or set of messages.
I will go ahead and add the row message. Should I cut a new version
of astroda right away?