[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New FITS Header
Rob,
Thanks Shawn, this is exactly what I am looking for, problems in the format.
Looks like Shawn has discovered a problem in DATE and DATE-OBS. I get
DATE-OBS time part directly from TIME$. I don't see how I could miss an
hour. What do you do?
Tom Droege
At 08:55 PM 4/9/01 -0400, you wrote:
>Ok, how about the DATE vs DATE-OBS keywords? Was the FITS file really
>created an hour before the exposure? Maybe this would speed up the
>downloads - create all the files you think you might need for the night ;)
>
>Shawn
>
>
>----- Original Message -----
>From: "Tom Droege" <tdroege@veriomail.com>
>To: "Tom Droege" <tdroege@veriomail.com>; <tass@listserv.wwa.com>
>Sent: Monday, April 09, 2001 6:59 PM
>Subject: Re: New FITS Header
>
>
> > OK, I have found one error, let's see if anyone else can find it or
>others.
> >
> > Tom Droege
> >
> > At 05:43 PM 4/9/01 -0500, you wrote:
> > >Fits Fans, here is the latest version of the fits header that I am
>writing
> > >on the data I take tonight. Please, fits experts, read this carefully.
>I
> > >want to get to the point where I can take "keeper" data with TOM. It
>will
> > >not be worth processing (I suspect) if the header is not in near final
>form.
> > >
> > >Tom Droege
> > >
> > >SIMPLE = T / file does conform to FITS standard
> > >BITPIX = 16 / number of bits per data pixel
> > >NAXIS = 2 / number of data axes
> > >NAXIS1 = 2043 / length of data axis 1
> > >NAXIS2 = 2037 / length of data axis 2
> > >EXTEND = T / FITS dataset may contain extensions
> > >COMMENT FITS (Flexible Image Transport System) format defined in
> > >Astronomy and
> > >COMMENT Astrophysics Supplement Series v44/p363, v44/p371, v73/p359,
> > >v73/p365.
> > >COMMENT Contact the NASA Science Office of Standards and Technology for
>the
> > >COMMENT FITS Definition document #100 and other FITS information.
> > >DATE = '2001-04-09T21:21:23' / file creation date (YYYY-MM-DDThh:mm:ss
>UTC)
> > >FILTER = 'V '
> > >LATITUDE= 41.8271 / Site H latitude, degrees north
> > >LONGITUD= -88.3125 / Site H longitude, degrees east
> > >RALIM = -9.5 / RA Limit Switch Position Degrees East
> > >DECLIM = 0. / Declination limit switch Degrees North
> > >DATASEC = '[ 17:2064, 1:2048]' / Place keeper for Active area of the
>detector
> > >BIASSEC = '[ 10: 15, 1:2048]' / Place keeper for Under-Over scan region
> > >TIMESYS = 'UT ' / time system for exposure start
> > >EPOCH = 2001. / Place keeper for Epoch of coordinates
> > >EQUINOX = 2000. / Place keeper for Equinox of coordinates
> > >SCALE = 7.4 / Arc seconds per pixel
> > >TIMEBASE= 'Manual GPS' / By hand transfer to PC clock
> > >COMMENT Additions to Constant File
> > >RA = '4:31:8.97' / RA of Field Center
> > >CRVAL1 = 4.52471659378365 / RA of Field Center
> > >RATIME = '1.976563' / Seconds since turning on RA drive
> > >IMAGETYP= 'object ' / object frame
> > >WATERTMP= '26.92675' / Cooling water temperature
> > >VCOTEMP = '32.45043' / VCO Temperature
> > >DEC = '0:00:00 ' / Place Keeper for DEC of field center
> > >CRVAL2 = '0 ' / Place Keeper for DEC of field center
> > >UT = '22:21:18' / Universal time of #0 exposure (V) start
> > >COMMENT This is the #0 Camera File
> > >DATE-OBS= '2001-04-09T22:21:18' / UT date-time of exposure start
> > >UTSTART = '22:21:18' / Universal time of #0 exposure (V) start
> > >EXPTIME = 99.85938 / Open Time for Camera 0 usually V
> > >GAIN = 2.5 / Place Keeper for Gain in electrons per
>adu
> > >RDNOISE = 25. / Place Keeper for Read Noise in electrons
> > >CDTEMP = '4.77099 ' / CCD Temperature Camera 0
> > >END
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >