From: Robert Lupton
Date: Tue, 25 Jan 2000 10:53:40 -0700 (MST)
Subject: obs log
Scot Kleinman writes:
 >                         January 24/5, 2000
 >
 >                    Apache Point Observatory SDSS 2.5m
 >
 >                            Observing Log
 >
 >                            (MJD 51568)
...
 >
 > Around 19:00. we started a goDrift -bias which seemed to be behaving ok.
 > The watcher, however, reported MCP axes abort errors and we do not
 > understand why this is so. A stop button was in, but the telescope should
 > not have been trying to move during a -bias goDrift, right?
The axes were in this state prior to starting the run; the error was
only reported when the exposure started.
 >
 > The watcher also reported out of spec BiasL and BiasRs for chips
 > 15,25,35,45, and 55.
The biasL and biasR were almost certainly really bad for chips 15, 25,
35, 45, and 55.  If I knew the run number I could check -- it'd be
helpful to include that in the observing log.  Hmm, actually they are
bad in all 3 runs. The bias in dewar 5 is indeed very high; I've sent
mail to cmr to find out what's going on.
 >  There were no bias values (not even the value
 > "(none)" displayed for chips 60-76 and 81-95.
Those are the astrometric chips, and astroline doesn't estimate biases
or much else for them.
"none" is used when there might be a value, e.g. the astrom CCDs are
paired, and one of each pair has a heaterv (this is at least
approximately correct).  The one that doesn't is labelled "none". In
the case of astroline where _none_ of the astrom chips are processed,
we simply leave them blank.  Would you prefer "none"? That's easy; in
fact I'd simply have to check in the change.
 >
 > The Focus Servo Subway (whatever that means) was also reporting bad focus.
 >
The chips are named:
	o l r i u z g t s
which stand for:
	overpass leading r i u z g trailing subway
(blame Jeff Pier). the Shu-i mnemonic is
	Our Lamentable Robert Is Under Ze Gunn, They Say
 > Why is it doing this when we are just doing a bias? No bug reports were
 > submitted for these two issues as we were not sure we understood what it is
 > supposed to be doing.  We'd be happy to submit proper bug reports later if
 > merited.  I guess the watcher doesn't know the difference between a -bias
 > goDrift and a data goDrift, so it will complain about things that aren't
 > errors at times.  If this can't be helped, so be it, but anything we can do
 > to avoid irrelevant, incorrect, unnecessary watcher errors, would
 > further enhance the esteem in which we hold the watcher.
 >
It is only supposed to look at focus when the shutters are open.  I'll
have to take a look.  Maybe someone can repeat this during the day, or
let me know when they'll be doing biases so that I can stay late?
 >
 > im>endNight 51568
 > endNight parseMurmur:
 > Mon Jan 24 22:37:28 MST 2000: Can't open 51568: No such file or directory
 > Error: Can't open 51568: No such file or directory
 >
I'd guess that this was something that I broke in response to a desire
to support the reading of more than one murmur log.  Jim (Annis): did
you test that change in the context of endNight?
					R