Date: Mon, 22 Jan 2007 10:17:41 -0600
From: John Hendry
Subject: Re: MJD 54113 idReport has no record of run 6672
Hi Shannon, Elena, Mike,
I appreciate everyone's effort to follow procedures
and thank everyone for their replies.
No big deal, I make plenty of mistakes too.
I was mostly concerned something was amiss with the software.
Thanks again,
John
On 01/19/2007 02:44 AM, Shannon Watters wrote:
> Hello,
>
> I think I may have forgotten to answer the final question for the final
> imager bias before endNight was run.  I remember having a problem
> getting the imager t-bar status (cc imstat) from the telescope enclosure
> and when I returned to the control room iop was still prompting me for a
> comment about run 6672.  After that the 'cc imstat' command worked but I
> think endNight had already been run.
>
> Sorry,
> Shannon
>
>
> On Jan 16, 2007, at 6:31 PM, Elena Malanushenko wrote:
>
>>  Hi, John,
>>
>> I was an observer that night.  I think Mike is right and we ran
>> endNight before
>> completing of  calibration and doing final bias. Sorry, our fault.
>>
>> Best regards,
>>
>> Elena Malanushenko
>> elenam@apo.nmsu.edu
>>
>>
>> Begin forwarded message:
>>
>>> From:  (Mike Harvanek)
>>> Date: January 16, 2007 6:03:02 PM MST
>>> Subject: Re: MJD 54113 idReport has no record of run 6672*
>>>
>>> Hi John,
>>>
>>> Run 6670 was the afternoon checkout bias.
>>> Run 6671 was the imager calibration data.
>>> Run 6672 was the bias that is taken after we take the
>>> imager out of staring mode (i.e., out of the imager
>>> calibration mode) and put it back into drift scanning mode.
>>>
>>>> why is there no trace of run 6672 in idReport?
>>>
>>> Perhaps the observers ran endNight before run 6672
>>> had completed.  This is just a guess, however, as I
>>> was not on duty that night.
>>>
>>>> adds to the manual work that I do
>>>
>>> Sorry about that John.  If this was due to a premature
>>> endNight, we'll do better.
>>>
>>> Mike Harvanek