FITS Headers
FIRAS_LINE_PROFILES_LHFA.FITS
Primary Header
SIMPLE = T / file does conform to FITS standard
BITPIX = 32 / number of bits per data pixel
NAXIS = 0 / number of data axes
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 = '28/09/97' / FITS file creation date (dd/mm/yy)
ORIGIN = 'CDAC ' / Cosmology Data Analysis Center
TELESCOP= 'COBE ' / COsmic Background Explorer satellite
INSTRUME= 'FIRAS ' / COBE instrument [DIRBE, DMR, FIRAS]
OBJECT = 'ALL-SKY ' / part of sky given [ALL-SKY, GAL-SLICE]
PRODUCT = 'HLINE-PR' / High frequency line profiles
EQUINOX = 2000.0 / equinox of coords in following tables
COMMENT
REFERENC= 'For additional information, please refer to the' /
REFERENC= 'COBE Far Infrared Absolute Spectrophotometer (FIRAS)' /
REFERENC= 'Explanatory Supplement, ed. J.C. Mather et al,' /
REFERENC= 'COBE Ref. Pub. No. 97-C (Greenbelt, MD: NASA/GSFC),' /
REFERENC= 'available in electronic form from the NSSDC.' /
COMMENT
COMMENT COBE specific keywords
DATE-BEG= '24/11/89' / date of initial data represented (dd/mm/yy)
DATE-END= '21/09/90' / date of final data represented (dd/mm/yy)
PIXRESOL= 6 / Quad tree pixel resolution [6, 9]
COMMENT
COMMENT FIRAS specific keywords
CHANSCAN= 'LHFA ' / Channel and mirror transport mechanism scan
COMMENT / mode identifier. The first two characters
COMMENT / indicate the channel, the first being the
COMMENT / instrument side: right (R) or left (L); and
COMMENT / the second being the frequency: high (H) or
COMMENT / low (L). The third and fourth characters
COMMENT / indicate the scan mode, the third being the
COMMENT / scan length: short (S) or long (L); and the
COMMENT / fourth being the scan speed: slow (S) or
COMMENT / fast (F). In addition, the scan mode may
COMMENT / take the following values for low frequency
COMMENT / data only (channel = RL or LL):
COMMENT / FS: decimated SF data;
COMMENT / FL: truncated LF data.
COMMENT / The scan mode value FA indicates: for high
COMMENT / frequency data (channel = RH or LH), a
COMMENT / combination of SF and LF data; and for low
COMMENT / frequency data (channel = RL or LL), a
COMMENT / combination of FS and FL data.
MODLLABL= 'PASS4 ' / FIRAS calibration model solution label
MISS_SEG= 'ENTIRE_MISSION' / FIRAS segment of mission represented
NU_ZERO = 68.020812 / Optical frequency of initial data point in GHz
DELTA_NU= 13.604162 / Optical frequency interval between data points
COMMENT / in GHz
NUM_FREQ= 210 / Number of frequency points with good data
END
Extension Header 2
XTENSION= 'BINTABLE' / Extension type is Binary Table
BITPIX = 8 / Binary data
NAXIS = 2 / Data are in a table
NAXIS1 = 15120 / Number of 8 bit bytes in each row
NAXIS2 = 1 / Number of rows
PCOUNT = 0 / Number of bytes of data following table
GCOUNT = 1 / Group count (always 1 for bintable extensions)
TFIELDS = 18 / Number of fields (columns) in the table
COMMENT
COMMENT
COMMENT FIRAS High Frequency Line Profiles
COMMENT Project Dataset Record Structure
COMMENT
COMMENT
COMMENT 115.27 GHz CO (J=1-0) line profile, in cm*MJy/(nanowatts/m^2)
TFORM1 = '210E ' /
TDIM1 = '(210) ' /
TTYPE1 = 'CO_115 ' / entire fieldname = CO_115
TUNIT1 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 230.54 GHz CO (J=2-1) line profile, in cm*MJy/(nanowatts/m^2)
TFORM2 = '210E ' /
TDIM2 = '(210) ' /
TTYPE2 = 'CO_230 ' / entire fieldname = CO_230
TUNIT2 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 345.80 GHz CO (J=3-2) line profile, in cm*MJy/(nanowatts/m^2)
TFORM3 = '210E ' /
TDIM3 = '(210) ' /
TTYPE3 = 'CO_345 ' / entire fieldname = CO_345
TUNIT3 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 424.75 GHz O2 line profile, in cm*MJy/(nanowatts/m^2)
TFORM4 = '210E ' /
TDIM4 = '(210) ' /
TTYPE4 = 'O2_424 ' / entire fieldname = O2_424
TUNIT4 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 461.04 GHz CO (J=4-3) line profile, in cm*MJy/(nanowatts/m^2)
TFORM5 = '210E ' /
TDIM5 = '(210) ' /
TTYPE5 = 'CO_461 ' / entire fieldname = CO_461
TUNIT5 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 492.23 GHz [C I] line profile, in cm*MJy/(nanowatts/m^2)
TFORM6 = '210E ' /
TDIM6 = '(210) ' /
TTYPE6 = 'C_I_492 ' / entire fieldname = C_I_492
TUNIT6 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 556.89 GHz H2O line profile, in cm*MJy/(nanowatts/m^2)
TFORM7 = '210E ' /
TDIM7 = '(210) ' /
TTYPE7 = 'H2O_556 ' / entire fieldname = H2O_556
TUNIT7 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 576.27 GHz CO (J=5-4) line profile, in cm*MJy/(nanowatts/m^2)
TFORM8 = '210E ' /
TDIM8 = '(210) ' /
TTYPE8 = 'CO_576 ' / entire fieldname = CO_576
TUNIT8 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 691.47 GHz CO (J=6-5) line profile, in cm*MJy/(nanowatts/m^2)
TFORM9 = '210E ' /
TDIM9 = '(210) ' /
TTYPE9 = 'CO_691 ' / entire fieldname = CO_691
TUNIT9 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 809.44 GHz [C I] line profile, in cm*MJy/(nanowatts/m^2)
TFORM10 = '210E ' /
TDIM10 = '(210) ' /
TTYPE10 = 'C_I_809 ' / entire fieldname = C_I_809
TUNIT10 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 1113.3 GHz H2O line profile, in cm*MJy/(nanowatts/m^2)
TFORM11 = '210E ' /
TDIM11 = '(210) ' /
TTYPE11 = 'H2O_1113' / entire fieldname = H2O_1113
TUNIT11 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 1461.1 GHz [N II] line profile, in cm*MJy/(nanowatts/m^2)
TFORM12 = '210E ' /
TDIM12 = '(210) ' /
TTYPE12 = 'N_II_146' / entire fieldname = N_II_1461
TUNIT12 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 1716.6 GHz H2O (J=2-1) line profile, in cm*MJy/(nanowatts/m^2)
TFORM13 = '210E ' /
TDIM13 = '(210) ' /
TTYPE13 = 'H2O_1716' / entire fieldname = H2O_1716
TUNIT13 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 1900.5 GHz [C II] line profile, in cm*MJy/(nanowatts/m^2)
TFORM14 = '210E ' /
TDIM14 = '(210) ' /
TTYPE14 = 'C_II_190' / entire fieldname = C_II_1900
TUNIT14 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 2060.1 GHz [O I] line profile, in cm*MJy/(nanowatts/m^2)
TFORM15 = '210E ' /
TDIM15 = '(210) ' /
TTYPE15 = 'O_I_2060' / entire fieldname = O_I_2060
TUNIT15 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 2311.7 GHz [Si I] line profile, in cm*MJy/(nanowatts/m^2)
TFORM16 = '210E ' /
TDIM16 = '(210) ' /
TTYPE16 = 'SI_I_231' / entire fieldname = SI_I_2311
TUNIT16 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 2459.4 GHz [N II] line profile, in cm*MJy/(nanowatts/m^2)
TFORM17 = '210E ' /
TDIM17 = '(210) ' /
TTYPE17 = 'N_II_245' / entire fieldname = N_II_2459
TUNIT17 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT 2589.6 GHz CH (J=2-1) line profile, in cm*MJy/(nanowatts/m^2)
TFORM18 = '210E ' /
TDIM18 = '(210) ' /
TTYPE18 = 'CH_2589 ' / entire fieldname = CH_2589
TUNIT18 = 'cm*MJy/(nanowatts/m^2)' /
COMMENT
END