From: stephanie snedden
Subject: Re: 2.5m obslog 20080130 (MJD 54496)
Date: Thu, 31 Jan 2008 12:10:40 -0700
I believe this is all related to a full pool disk problem that
occurred in the afternoon. Shannon can provide details about this.
Steph
On Jan 31, 2008, at 5:30 AM, Dan Oravetz wrote:
>
>
>
> We had problems running endNight, so we ran it manually and in the
> step-by-step fashion and it still hung up on two commands (see log).
>
> ---=== OBSERVING LOG ===---
>
> Afternoon:
> ---------
> All systems checked.
>
> Watcher warning for Astroloine->chip 33:  biasL, nQuartileL (known
> cold
> issue).  Took a bias with the T-bars unlatched but chip 33 had the
> same issue.
> Took another bias after relatching the T-bars.  Chip 33 looked
> better but
> slowly degraded and the same watcher warning appeared.
>
>
>
> 12:10Z - endNight was hung up for about 10 minutes after we told it to
> continue after it asked about which PT frames it thought were on
> disk.  We did
> a CTRL-C and tried again and this time it got hung at the very
> beginning...we
> never got anything returned after we entered 'endNight.'  We then
> tried
> running endNight manually and step-by-step according to the SDSS DA
> endNight
> Procedures page, and the 'verifyImagerFilesOnDisk' command hung up
> and we had
> to CTRL-C out again.  Next time we skipped the ImagerFiles command
> and instead
> went on to try the 'verifySpectroFilesOnDisk' command and that
> worked fine, as
> well as everything up until the 'createIdApoDiskLog' command which
> also hung.
> So, it would seem that imager data related information is what was
> having
> trouble?  Furthermore, in the Imaging Summary section of the log,
> there are
> some unusual entries following the first two runs, so the third
> bias run did
> not show up in the usual manner.
>
>