HELLRIDE Header
Sample of current HELLRIDE header:
SIMPLE = T / file does conform to FITS standard
BITPIX = 16 / number of bits per data pixel
NAXIS = 3 / number of data axes
NAXIS1 = 1440 / length of data axis 1
NAXIS2 = 1440 / length of data axis 2
NAXIS3 = 31 / length of data axis 3
EXTEND = T / FITS dataset may contain extensions
COMMENT FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
BZERO = 32768 / offset data range to that of unsigned short
BSCALE = 1 / default scaling factor
DATE-BEG= '2020-09-06T08:40:30' / Date and time of beginning of observation
DATE-OBS= '2020-09-06T08:40:30' / Same as DATE_OBS, for other compliances
OBSRVTRY= 'Teide Observatory' / Observatory name
TELESCOP= 'VTT ' / Telescope name
INSTRUME= 'HELLRIDE' / Instrument name
FILTER = 'Na_I_D2_5890' / Spectral line ID
WAVEUNIT= 4.79864766250306E-038 / Wavelength uint (Angstrom)
OBS_MODE= 'Science ' / Mode of data acquisition
AWAVLNTH= 5890. / Nominal wavelegnth of observation
DETECTOR= 'Andor Zyla 5.5 USB' / Detector make and model
TEXPOSUR= 0.0200033802816901 / Exposure time in seconds
BINNING = '1x1 ' / Binning
OBSERVER= ' ' / Names of observers
PLANNER = ' ' / Names of planners
NACCUM = 1 / Numbers of frames stacked up
NWAVES = 31 / Number of wavelength points
WAVESCAN= 3. / Wavelength scan range
IFWAVE = 5892. / Interference filter's wavelength
IFPASS = 6.7 / Interference filter's passband
ATMOS_R0= 0. / Fried's parameter
DATATAGS= ' ' / Other settings
ET1STEP = 1.81097906055461 / Etalon 1 step counts
ET2STEP = 13.8705248394478 / Etalon 2 step counts
ET1ZERO = 227. / Etalon 1 line center counts
ET2ZERO = 506. / Etalon 2 line center counts
DATE-END= '020-09-06T08:40:33' / Date and time of beginning of observation
END This does not comply to SOLARNET, and is missing relevant information such as Coordinate information and further specification of what the data actually means. The L1 header will be implemented at sometime in the future which will contain much the same information with some additional fields which are not yet further specified.
We need to make sure that the L1 header is up to scratch before too much data is produced.