About midnight (we were outdoors closing up), watcher reported an error on i+trim2.  When
we looked at the watcher display, we were fooled into thinking there was a problem on
CCD61 (which us neophytes did not know ALWAYS shows a wrong i+trim2).  In any case, the
underlying problem seems to have been the regular reboot of the camera several days after
a power cycle (or testing the panic button, as done during shakedown).  We are glad
Connie was not asleep when we phoned her! :-}

Menawhile, Jurek's sop session (xterm and GUI) and telrun had hung.  We were not sure if
the spectrographs had been left in an indeterminate state, so Pete issued commands in his
sop window, getting an error:


sp2> initNight   
Tue Aug 14 00:40:35 MDT 2001: SOP Ready for flight
rpc.pcnfsd appears to be running - good.
nfsd appears to be registered - good.
sp2> goStare 0 -init -bias
PlateId [-9999]: 
cameraData(exec_boot) does not exist!!!!!!!
   camstat     does not seem to have worked
Flushing charge for 15 sec
appending BEGIN
appending END
EXPOSURE TIME is:  0
997771307 997771307
The old teamster, PID 1466794, appears to have died; restarting
Seq 10530 Exp 10530 Frame 10530
Do not schedule startFlushCharge sp1 200
sp2>
Do not schedule startFlushCharge sp2 200


The s4l output from sop is confused:

sp1> s4l    
 UT    Exp   Time  flavor     comment
===============================================
 ----- sequence 10525, plate -9999 -------
 20:26 10525 0.0    bias        {{}}
 01:04 10526 0.0    bias        {{}}
 01:27 10527 0.0    bias        {{}}
 ----- sequence 10528, plate 636 -------
 05:21 10528 10.0   flat        pre-flat
 05:23 10529 2.0    arc         pre-arc
 ----- sequence 10530, plate -9999 -------
 06:42 10530 0.0    bias        science science {{}}
 06:46 10531 0.0    bias        {{}}
 08:01 10532 0.0    bias        {{}}
 08:05 10533 0.0    bias        {{}}