From: Craig Loomis
Date: Sat, 14 Apr 2012 09:14:00 -0400
Subject: Re: [sdss3-25mlog 622] 2.5m obslog 20120413 (MJD 56031)
On Sat, Apr 14, 2012 at 07:49,   wrote:
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 APACHE POINT OBSERVATORY SDSS 2.5M
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 OBSERVING LOG
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0Friday April 13, 2012
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(MJD 56031)
> Cart. 15, 5466
> **************
> 08:30:43 =C2=A0boss exposure =C2=A0 =C2=A04.0, file=3D142387
>
> We had a hung readout. We issued a 'reloadControllers', an 'exposure reco=
ver',
> and a 'clearExposure'. The next set of calibration exposures read-out fin=
e.
>
> 08:41:44 =C2=A0boss exposure =C2=A0 =C2=A04.0, file=3D142389
   Ah, finally! Thank you for running/testing that correct procedure.
The good news is that the recovery appears to have worked: the 142388
files look good. Specifically, the data in the two pairs of sp1
exposures are identical, and the recovered sp2 exposures look like
well formatted arcs. [can someone check that in detail?]  The bad news
is that they were put in a strange place (pwd was
$BOSS_DIR/python/boss): the recovery code clearly did not know the
directory. I just moved them in to /data/spectro/56031 and added them
to the sha1 file; I think it is early enough in the day that the SAS
copy hasn't started....
   One procedure tweak. Once the directory bug is fixed, I suggest
that all files from the failed readout be declared bad, and that for
further processing all four parts from the recovered one be used. Not
sure how best to slap sos to make that happen at APO.
 - craig