Coming Runs

[droege@snapmail.us]

I am getting set up for the comming run season.  With Rob's software, I
think I can do a workman like job.

I would like *not* to have a log book.  I want to put all log book type
entries in the .fits header.  I think that it what it was meant for.  If
something is too long to put in the fits header, then I will make an
"operating note" of it and put it in Michael's data base.  Some of this
type of thing is already in the "service notes".  The service notes will
do fine for this purpose.  In this case I would just put in the .fits
header "service note 23 performed".

Things I can think of to put in the fits header:

mount rotated to 342.4 from 341.1 (date)
v and i lens cleaned (date)
now running software version 3.1.2 (date)
RA drive failed and was re-lined with chamois (date)

These items would generally stay in the header until replaced.  So you
could look at any image, for example, and find when the lenses were last
cleaned.

I would expect that as time goes on we would add more and more comment
lines.  Space is cheap.

Any suggestions as to what should be put in the header?

Any comments as to whether a log book should be kept?

My intenton at the moment, is to make darks every night and to make flats
from from time to time with good data - though this may not be the right
strategy.

Tom Droege