Re: FITS header values

[<aah@nofs.navy.mil>]

  I have been working on software for the IR camera
and have not had time to participate in this
discussion.  It is snowing now, so I have a few moments
to write emails and continue with the GRB010222 paper.
 One problem with Michael's definition of CDELT2
(the RA increment).  This would then change at every
new declination setting.
  Before you say 'fooey', you should read the new
standard for WCS thoroughly and make sure you
understand it, as there are usually reasons why
things change.  Since the Mark IV will run for the
next 5-10 years (it will at NOFS, anyway), I think
we should do it right where possible.
  While keyword order makes no difference as far
as most FITS readers are concerned, it does make
the header cleaner and easier for a human to read
if you group like parameters together.  For example,
Tom is including  DATE and DATE-OBS; place them on
adjacent lines.  Same with UT, UTSTART and TIMESYS
(I normally consider them in the 'date' group);
coordinates; temperatures; etc.
The comments about FITS Definition documents should
be placed at the end of the header.
  BZERO and BSCALE should definitely be in the fits
header.  I don't recall; perhaps cfitsio adds them
automatically when it writes the file.
  The easiest and most practical way to get proper
UT is to run your computer on UT.  You never have
to worry about conversions or daylight savings time.
Arne