Semantics of FITS file NICMOSn4hk12010_mos.fits
SemanticRepresentationInformation
· http://example.org/archive/semantic-representation-information-d8c057ad
Write it out
Download the data description →
Its Representation Information, with all it needs, as a zip: description.ttl and each structure description and view specification (DFDL, Kaitai Struct, DRB, ...) as a file.
Its Archival Information Package
Properties
| comment | Semantics of "FITS file NICMOSn4hk12010_mos.fits": Described from its headers, by archive-manager's RepInfo Tools (FITS Standard 4.0, https://fits.gsfc.nasa.gov/fits_standard.html): 6 HDUs. hdu1: HDU 1, the primary HDU, with no data hdu2: HDU 2, an image extension (EXTNAME 'SCI'), a 270 x 263 array hdu3: HDU 3, an image extension (EXTNAME 'ERR'), a 270 x 263 array hdu4: HDU 4, an image extension (EXTNAME 'DQ'), a 270 x 263 array hdu5: HDU 5, an image extension (EXTNAME 'SAMP'), a 270 x 263 array hdu6: HDU 6, an image extension (EXTNAME 'TIME'), a 270 x 263 array Each header is a record of its keyword records, 80 characters each, with what each keyword means from the FITS Standard's dictionary; each table's columns and each image's pixels are typed, named and given units, scale, offset and fill value as the header says. - hdu1_header: Header of HDU 1, the primary HDU, with no data: The header of HDU 1, the primary HDU, with no data: 252 keyword records of 80 ASCII characters, the last END, in 7 blocks. - hdu1_header.simple: SIMPLE: The value field shall contain a logical constant with the value T if the file conforms to this Standard. This keyword is mandatory for the primary header and must not appear in extension headers.7 A value of F signifies that the file does not conform to this Standard. This record's comment: "Fits standard" - hdu1_header.bitpix: BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two's complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record's comment: "Bits per pixel" - hdu1_header.naxis: NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record's comment: "Number of axes" - hdu1_header.extend: EXTEND: The value field shall contain a logical value indicating whether the FITS file is allowed to contain conforming extensions following the primary HDU. This record's comment: "File may contain extensions" - hdu1_header.origin: ORIGIN: The value field shall contain a character string identifying the organization or institution responsible for creating the FITS file. This record's comment: "FITS file originator" - hdu1_header.iraf_tlm: IRAF-TLM: A keyword the FITS Standard doesn't define. - hdu1_header.nextend: NEXTEND: A keyword the FITS Standard doesn't define. This record's comment: "Number of standard extensions" - hdu1_header.date: DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. - hdu1_header.filename: FILENAME: A keyword the FITS Standard doesn't define. This record's comment: "name of file" - hdu1_header.filetype: FILETYPE: A keyword the FITS Standard doesn't define. This record's comment: "type of data found in data file" - hdu1_header.blank: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.telescop: TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record's comment: "telescope used to acquire data" - hdu1_header.instrume: INSTRUME: The value field shall contain a character string identifying the instrument used to acquire the data associated with the header. This record's comment: "identifier for instrument used to acquire data" - hdu1_header.equinox: EQUINOX: The epoch of the mean equator and equinox, in years, for celestial coordinate systems based on a mean equator and equinox (FK4, FK5); EQUINOXa for an alternate coordinate description a. This record's comment: "equinox of celestial coord. system" - hdu1_header.blank_2: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_3: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_4: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.rootname: ROOTNAME: A keyword the FITS Standard doesn't define. This record's comment: "rootname of the observation set" - hdu1_header.imagetyp: IMAGETYP: A keyword the FITS Standard doesn't define. This record's comment: "type of exposure identifier" - hdu1_header.primesi: PRIMESI: A keyword the FITS Standard doesn't define. This record's comment: "instrument designated as prime" - hdu1_header.blank_5: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_6: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_7: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.targname: TARGNAME: A keyword the FITS Standard doesn't define. This record's comment: "proposer's target name" - hdu1_header.ra_targ: RA_TARG: A keyword the FITS Standard doesn't define. This record's comment: "right ascension of the target (deg) (J2000)" - hdu1_header.dec_targ: DEC_TARG: A keyword the FITS Standard doesn't define. This record's comment: "declination of the target (deg) (J2000)" - hdu1_header.ecl_long: ECL_LONG: A keyword the FITS Standard doesn't define. This record's comment: "ecliptic longitude of the target (deg) (J2000)" - hdu1_header.ecl_lat: ECL_LAT: A keyword the FITS Standard doesn't define. This record's comment: "ecliptic latitude of the target (deg) (J2000)" - hdu1_header.gal_long: GAL_LONG: A keyword the FITS Standard doesn't define. This record's comment: "galactic longitude of the target (deg) (J2000)" - hdu1_header.gal_lat: GAL_LAT: A keyword the FITS Standard doesn't define. This record's comment: "galactic latitude of the target (deg) (J2000)" - hdu1_header.blank_8: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_9: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_10: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.proposid: PROPOSID: A keyword the FITS Standard doesn't define. This record's comment: "PEP proposal identifier" - hdu1_header.linenum: LINENUM: A keyword the FITS Standard doesn't define. This record's comment: "proposal logsheet line number" - hdu1_header.pr_inv_l: PR_INV_L: A keyword the FITS Standard doesn't define. This record's comment: "last name of principal investigator" - hdu1_header.pr_inv_f: PR_INV_F: A keyword the FITS Standard doesn't define. This record's comment: "first name of principal investigator" - hdu1_header.pr_inv_m: PR_INV_M: A keyword the FITS Standard doesn't define. This record's comment: "middle name / initial of principal investigat" - hdu1_header.blank_11: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_12: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_13: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.orientat: ORIENTAT: A keyword the FITS Standard doesn't define. This record's comment: "position angle of image y axis (deg. e of n)" - hdu1_header.sunangle: SUNANGLE: A keyword the FITS Standard doesn't define. This record's comment: "angle between sun and V1 axis" - hdu1_header.moonangl: MOONANGL: A keyword the FITS Standard doesn't define. This record's comment: "angle between moon and V1 axis" - hdu1_header.sun_alt: SUN_ALT: A keyword the FITS Standard doesn't define. This record's comment: "altitude of the sun above Earth's limb" - hdu1_header.fgslock: FGSLOCK: A keyword the FITS Standard doesn't define. This record's comment: "commanded FGS lock (FINE,COARSE,GYROS,UNKNOWN)" - hdu1_header.blank_14: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.date_obs: DATE-OBS: The format of the value field for DATE-OBS keywords shall follow the prescriptions for the DATE keyword (Sect. 4.4.2 and Sect. 9.1.1 Either the four-digit year format or the two-digit year format may be used for observation dates from 1900 through 1999, although the four-digit format is recommended. This record's comment: "UT date of start of observation (yyyy-mm-dd)" - hdu1_header.time_obs: TIME-OBS: A keyword the FITS Standard doesn't define. This record's comment: "UT time of start of observation (hh:mm:ss)" - hdu1_header.expstart: EXPSTART: A keyword the FITS Standard doesn't define. This record's comment: "exposure start time (Modified Julian Date)" - hdu1_header.expend: EXPEND: A keyword the FITS Standard doesn't define. This record's comment: "exposure end time (Modified Julian Date)" - hdu1_header.exptime: EXPTIME: A keyword the FITS Standard doesn't define. This record's comment: "exposure duration (seconds)--calculated" - hdu1_header.expflag: EXPFLAG: A keyword the FITS Standard doesn't define. This record's comment: "Exposure interruption indicator" - hdu1_header.blank_15: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_16: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_17: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.camera: CAMERA: A keyword the FITS Standard doesn't define. This record's comment: "Camera in use (1, 2, or 3)" - hdu1_header.primecam: PRIMECAM: A keyword the FITS Standard doesn't define. This record's comment: "Primary camera for internal parallels" - hdu1_header.focus: FOCUS: A keyword the FITS Standard doesn't define. This record's comment: "In-focus camera for this observation" - hdu1_header.aperture: APERTURE: A keyword the FITS Standard doesn't define. This record's comment: "aperture in use (NICi,NICi-FIX,NIC2-CORON/ACQ)" - hdu1_header.obsmode: OBSMODE: A keyword the FITS Standard doesn't define. This record's comment: "array readout mode (ACCUM, MULTIACCUM, etc.)" - hdu1_header.filter: FILTER: A keyword the FITS Standard doesn't define. This record's comment: "filter wheel element in beam during observation" - hdu1_header.numiter: NUMITER: A keyword the FITS Standard doesn't define. This record's comment: "number of exposure iterations" - hdu1_header.nread: NREAD: A keyword the FITS Standard doesn't define. This record's comment: "ACCUM - number of initial and final readouts" - hdu1_header.nsamp: NSAMP: A keyword the FITS Standard doesn't define. This record's comment: "RAMP, MULTI-ACCUM - number of samples" - hdu1_header.samp_seq: SAMP_SEQ: A keyword the FITS Standard doesn't define. This record's comment: "MultiAccum exposure time sequence name" - hdu1_header.cr_elim: CR_ELIM: A keyword the FITS Standard doesn't define. This record's comment: "RAMP - onboard cosmic ray detection used" - hdu1_header.sat_elim: SAT_ELIM: A keyword the FITS Standard doesn't define. This record's comment: "RAMP - on-board saturation detection used" - hdu1_header.crthresh: CRTHRESH: A keyword the FITS Standard doesn't define. This record's comment: "RAMP - on-board cosmic ray detect threshold" - hdu1_header.sathresh: SATHRESH: A keyword the FITS Standard doesn't define. This record's comment: "RAMP - on-board saturation threshold" - hdu1_header.varscale: VARSCALE: A keyword the FITS Standard doesn't define. This record's comment: "RAMP - on-board scale factor for variance" - hdu1_header.fomxpos: FOMXPOS: A keyword the FITS Standard doesn't define. This record's comment: "X offset of FOV using NICMOS FOM (arcsec)" - hdu1_header.fomypos: FOMYPOS: A keyword the FITS Standard doesn't define. This record's comment: "Y offset of FOV using NICMOS FOM (arcsec)" - hdu1_header.nfxtiltp: NFXTILTP: A keyword the FITS Standard doesn't define. This record's comment: "Fom X TILT Position (arcsec)" - hdu1_header.nfytiltp: NFYTILTP: A keyword the FITS Standard doesn't define. This record's comment: "Fom Y TILT Position (arcsec)" - hdu1_header.npxtiltp: NPXTILTP: A keyword the FITS Standard doesn't define. This record's comment: "PAM X TILT Position (steps)" - hdu1_header.npytiltp: NPYTILTP: A keyword the FITS Standard doesn't define. This record's comment: "PAM Y TILT Position (steps)" - hdu1_header.npfocusp: NPFOCUSP: A keyword the FITS Standard doesn't define. This record's comment: "Pam FOCUS Position (mm)" - hdu1_header.timepatt: TIMEPATT: A keyword the FITS Standard doesn't define. This record's comment: "timing pattern id" - hdu1_header.readout: READOUT: A keyword the FITS Standard doesn't define. This record's comment: "detector array readout rate (FAST, SLOW)" - hdu1_header.sampzero: SAMPZERO: A keyword the FITS Standard doesn't define. This record's comment: "sample time of the zeroth read (sec)" - hdu1_header.hclkrate: HCLKRATE: A keyword the FITS Standard doesn't define. This record's comment: "horizontal clock rate (microseconds)" - hdu1_header.video_bw: VIDEO_BW: A keyword the FITS Standard doesn't define. This record's comment: "readout video bandwidth (kHz)" - hdu1_header.adcgain: ADCGAIN: A keyword the FITS Standard doesn't define. This record's comment: "analog-digital conversion gain (electrons/DN)" - hdu1_header.blank_18: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_19: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_20: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.backest1: BACKEST1: A keyword the FITS Standard doesn't define. This record's comment: "background estimate number 1" - hdu1_header.backest2: BACKEST2: A keyword the FITS Standard doesn't define. This record's comment: "background estimate number 2" - hdu1_header.backest3: BACKEST3: A keyword the FITS Standard doesn't define. This record's comment: "background estimate number 3" - hdu1_header.blank_21: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_22: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_23: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.photmode: PHOTMODE: A keyword the FITS Standard doesn't define. - hdu1_header.photflam: PHOTFLAM: A keyword the FITS Standard doesn't define. This record's comment: "inverse sensitivity (ergs/cm**2/Angstrom/DN)" - hdu1_header.photfnu: PHOTFNU: A keyword the FITS Standard doesn't define. This record's comment: "inverse sensitivity (JY*sec/DN)" - hdu1_header.photzpt: PHOTZPT: A keyword the FITS Standard doesn't define. This record's comment: "ST magnitude system zero point (mag)" - hdu1_header.photplam: PHOTPLAM: A keyword the FITS Standard doesn't define. This record's comment: "pivot wavelength of the photmode (Angstroms)" - hdu1_header.photbw: PHOTBW: A keyword the FITS Standard doesn't define. This record's comment: "RMS bandwidth of the photmode (Angstroms)" - hdu1_header.blank_24: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_25: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_26: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.saa_exit: SAA_EXIT: A keyword the FITS Standard doesn't define. This record's comment: "time of last exit from SAA contour level 23" - hdu1_header.saa_time: SAA_TIME: A keyword the FITS Standard doesn't define. This record's comment: "seconds since last exit from SAA contour 23" - hdu1_header.saa_dark: SAA_DARK: A keyword the FITS Standard doesn't define. This record's comment: "association name for post-SAA dark exposures" - hdu1_header.saacrmap: SAACRMAP: A keyword the FITS Standard doesn't define. This record's comment: "SAA cosmic ray map file" - hdu1_header.blank_27: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_28: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_29: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.maskfile: MASKFILE: A keyword the FITS Standard doesn't define. This record's comment: "static data quality file" - hdu1_header.noisfile: NOISFILE: A keyword the FITS Standard doesn't define. This record's comment: "detector read noise file" - hdu1_header.nlinfile: NLINFILE: A keyword the FITS Standard doesn't define. This record's comment: "detector nonlinearities file" - hdu1_header.darkfile: DARKFILE: A keyword the FITS Standard doesn't define. This record's comment: "dark current file" - hdu1_header.tempfile: TEMPFILE: A keyword the FITS Standard doesn't define. This record's comment: "temperature-dependent dark file" - hdu1_header.flatfile: FLATFILE: A keyword the FITS Standard doesn't define. This record's comment: "flat field file" - hdu1_header.phottab: PHOTTAB: A keyword the FITS Standard doesn't define. This record's comment: "photometric calibration table" - hdu1_header.backtab: BACKTAB: A keyword the FITS Standard doesn't define. This record's comment: "background model parameters table" - hdu1_header.blank_30: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_31: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_32: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.maskpdgr: MASKPDGR: A keyword the FITS Standard doesn't define. This record's comment: "static data quality file" - hdu1_header.noispdgr: NOISPDGR: A keyword the FITS Standard doesn't define. This record's comment: "detector read noise file" - hdu1_header.nlinpdgr: NLINPDGR: A keyword the FITS Standard doesn't define. This record's comment: "detector nonlinearities f" - hdu1_header.darkpdgr: DARKPDGR: A keyword the FITS Standard doesn't define. This record's comment: "dark current file pedigre" - hdu1_header.flatpdgr: FLATPDGR: A keyword the FITS Standard doesn't define. This record's comment: "flat field file pedigree" - hdu1_header.photpdgr: PHOTPDGR: A keyword the FITS Standard doesn't define. This record's comment: "photometric calibration t" - hdu1_header.backpdgr: BACKPDGR: A keyword the FITS Standard doesn't define. This record's comment: "background model paramete" - hdu1_header.blank_33: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_34: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_35: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.biascorr: BIASCORR: A keyword the FITS Standard doesn't define. This record's comment: "subtract ADC bias level" - hdu1_header.zsigcorr: ZSIGCORR: A keyword the FITS Standard doesn't define. This record's comment: "Zero read signal correction" - hdu1_header.zoffcorr: ZOFFCORR: A keyword the FITS Standard doesn't define. This record's comment: "subtract MULTIACCUM zero read" - hdu1_header.maskcorr: MASKCORR: A keyword the FITS Standard doesn't define. This record's comment: "data quality initialization" - hdu1_header.noiscalc: NOISCALC: A keyword the FITS Standard doesn't define. This record's comment: "calculate statistic errors" - hdu1_header.nlincorr: NLINCORR: A keyword the FITS Standard doesn't define. This record's comment: "correct for detector nonlinearities" - hdu1_header.darkcorr: DARKCORR: A keyword the FITS Standard doesn't define. This record's comment: "dark correction" - hdu1_header.barscorr: BARSCORR: A keyword the FITS Standard doesn't define. This record's comment: "bars correction" - hdu1_header.flatcorr: FLATCORR: A keyword the FITS Standard doesn't define. This record's comment: "flat field correction" - hdu1_header.unitcorr: UNITCORR: A keyword the FITS Standard doesn't define. This record's comment: "convert to count rates" - hdu1_header.photcalc: PHOTCALC: A keyword the FITS Standard doesn't define. This record's comment: "calculate photometric keywords" - hdu1_header.cridcalc: CRIDCALC: A keyword the FITS Standard doesn't define. This record's comment: "identify cosmic ray hits" - hdu1_header.backcalc: BACKCALC: A keyword the FITS Standard doesn't define. This record's comment: "calculate background estimates" - hdu1_header.warncalc: WARNCALC: A keyword the FITS Standard doesn't define. This record's comment: "generate user warnings" - hdu1_header.blank_36: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_37: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_38: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.biasdone: BIASDONE: A keyword the FITS Standard doesn't define. This record's comment: "subtract ADC bias level" - hdu1_header.zsigdone: ZSIGDONE: A keyword the FITS Standard doesn't define. This record's comment: "Zero read signal correction" - hdu1_header.zoffdone: ZOFFDONE: A keyword the FITS Standard doesn't define. This record's comment: "subtract MULTI-ACCUM zero read" - hdu1_header.maskdone: MASKDONE: A keyword the FITS Standard doesn't define. This record's comment: "data quality initialization" - hdu1_header.noisdone: NOISDONE: A keyword the FITS Standard doesn't define. This record's comment: "calculate statistic errors" - hdu1_header.nlindone: NLINDONE: A keyword the FITS Standard doesn't define. This record's comment: "correct for detector nonlinearities" - hdu1_header.darkdone: DARKDONE: A keyword the FITS Standard doesn't define. This record's comment: "dark correction" - hdu1_header.barsdone: BARSDONE: A keyword the FITS Standard doesn't define. This record's comment: "bars correction" - hdu1_header.flatdone: FLATDONE: A keyword the FITS Standard doesn't define. This record's comment: "flat field correction" - hdu1_header.unitdone: UNITDONE: A keyword the FITS Standard doesn't define. This record's comment: "convert to count rates" - hdu1_header.photdone: PHOTDONE: A keyword the FITS Standard doesn't define. This record's comment: "calculate photometric keywords" - hdu1_header.criddone: CRIDDONE: A keyword the FITS Standard doesn't define. This record's comment: "identify cosmic ray hits" - hdu1_header.backdone: BACKDONE: A keyword the FITS Standard doesn't define. This record's comment: "calculate background estimates" - hdu1_header.warndone: WARNDONE: A keyword the FITS Standard doesn't define. This record's comment: "generate user warnings" - hdu1_header.blank_39: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.calstage: CALSTAGE: A keyword the FITS Standard doesn't define. This record's comment: "state of calibration" - hdu1_header.cal_ver: CAL_VER: A keyword the FITS Standard doesn't define. This record's comment: "CALNIC code version" - hdu1_header.proctime: PROCTIME: A keyword the FITS Standard doesn't define. This record's comment: "Pipeline processing time (MJD)" - hdu1_header.opus_ver: OPUS_VER: A keyword the FITS Standard doesn't define. This record's comment: "OPUS software system version number" - hdu1_header.blank_40: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_41: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_42: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.illmcorr: ILLMCORR: A keyword the FITS Standard doesn't define. This record's comment: "background illumination pattern subtraction" - hdu1_header.illmdone: ILLMDONE: A keyword the FITS Standard doesn't define. This record's comment: "background illumination pattern subtraction" - hdu1_header.illmfile: ILLMFILE: A keyword the FITS Standard doesn't define. This record's comment: "background illumination pattern file name" - hdu1_header.illmpdgr: ILLMPDGR: A keyword the FITS Standard doesn't define. This record's comment: "background illumination p" - hdu1_header.mean_bkg: MEAN_BKG: A keyword the FITS Standard doesn't define. This record's comment: "mean background level (DN/sec)" - hdu1_header.blank_43: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_44: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_45: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.pattern1: PATTERN1: A keyword the FITS Standard doesn't define. This record's comment: "primary pattern type" - hdu1_header.p1_shape: P1_SHAPE: A keyword the FITS Standard doesn't define. This record's comment: "primary pattern shape" - hdu1_header.p1_purps: P1_PURPS: A keyword the FITS Standard doesn't define. This record's comment: "primary pattern purpose" - hdu1_header.p1_npts: P1_NPTS: A keyword the FITS Standard doesn't define. This record's comment: "number of points in primary pattern" - hdu1_header.p1_pspac: P1_PSPAC: A keyword the FITS Standard doesn't define. This record's comment: "point spacing for primary pattern (arc-sec)" - hdu1_header.p1_lspac: P1_LSPAC: A keyword the FITS Standard doesn't define. This record's comment: "line spacing for primary pattern (arc-sec)" - hdu1_header.p1_angle: P1_ANGLE: A keyword the FITS Standard doesn't define. This record's comment: "angle between sides of parallelogram patt (deg)" - hdu1_header.p1_frame: P1_FRAME: A keyword the FITS Standard doesn't define. This record's comment: "coordinate frame of primary pattern" - hdu1_header.p1_orint: P1_ORINT: A keyword the FITS Standard doesn't define. This record's comment: "orientation of pattern to coordinate frame (deg" - hdu1_header.p1_centr: P1_CENTR: A keyword the FITS Standard doesn't define. This record's comment: "center pattern relative to pointing (yes/no)" - hdu1_header.bkg_off: BKG_OFF: A keyword the FITS Standard doesn't define. This record's comment: "pattern offset method (SAM or FOM)" - hdu1_header.pattstep: PATTSTEP: A keyword the FITS Standard doesn't define. This record's comment: "position number of this point in the pattern" - hdu1_header.patt_off: PATT_OFF: A keyword the FITS Standard doesn't define. This record's comment: "pattern offset method (SAM, FOM, etc.)" - hdu1_header.pattern: PATTERN: A keyword the FITS Standard doesn't define. This record's comment: "pattern type" - hdu1_header.porient: PORIENT: A keyword the FITS Standard doesn't define. This record's comment: "orientation of pattern on sky (deg)" - hdu1_header.numpos: NUMPOS: A keyword the FITS Standard doesn't define. This record's comment: "number of positions in pattern" - hdu1_header.dithsize: DITHSIZE: A keyword the FITS Standard doesn't define. This record's comment: "size of dither steps (arc seconds)" - hdu1_header.patt_pos: PATT_POS: A keyword the FITS Standard doesn't define. This record's comment: "position number in pattern sequence" - hdu1_header.blank_46: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_47: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_48: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.nchkboxx: NCHKBOXX: A keyword the FITS Standard doesn't define. This record's comment: "CHecKBOX location X" - hdu1_header.nchkboxy: NCHKBOXY: A keyword the FITS Standard doesn't define. This record's comment: "CHecKBOX location Y" - hdu1_header.ntaboxsz: NTABOXSZ: A keyword the FITS Standard doesn't define. This record's comment: "TA checkBOX SiZe" - hdu1_header.nxcent: NXCENT: A keyword the FITS Standard doesn't define. This record's comment: "X pos CENTroid (steps)" - hdu1_header.nycent: NYCENT: A keyword the FITS Standard doesn't define. This record's comment: "Y pos CENTroid (steps)" - hdu1_header.nxcentp: NXCENTP: A keyword the FITS Standard doesn't define. This record's comment: "X pos CENTroid (pixels)" - hdu1_header.nycentp: NYCENTP: A keyword the FITS Standard doesn't define. This record's comment: "Y pos CENTroid (pixels)" - hdu1_header.nboxsum: NBOXSUM: A keyword the FITS Standard doesn't define. This record's comment: "checkBoX SUM" - hdu1_header.noffsetx: NOFFSETX: A keyword the FITS Standard doesn't define. This record's comment: "OFFSET maneuver X (steps)" - hdu1_header.noffsety: NOFFSETY: A keyword the FITS Standard doesn't define. This record's comment: "OFFSET maneuver Y (steps)" - hdu1_header.noffstxp: NOFFSTXP: A keyword the FITS Standard doesn't define. This record's comment: "OFFSeT maneuver X (pixels)" - hdu1_header.noffstyp: NOFFSTYP: A keyword the FITS Standard doesn't define. This record's comment: "OFFSeT maneuver Y (pixels)" - hdu1_header.nslewcon: NSLEWCON: A keyword the FITS Standard doesn't define. This record's comment: "SLEW CONfirmation (Clear,Set)" - hdu1_header.blank_49: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_50: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_51: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.asn_id: ASN_ID: A keyword the FITS Standard doesn't define. This record's comment: "unique identifier assigned to association" - hdu1_header.asn_tab: ASN_TAB: A keyword the FITS Standard doesn't define. This record's comment: "name of the association table" - hdu1_header.asn_mtyp: ASN_MTYP: A keyword the FITS Standard doesn't define. This record's comment: "Role of the Member in the Association" - hdu1_header.blank_52: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_53: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_54: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_55: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_56: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_57: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_58: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_59: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_60: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_61: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_62: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_63: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_64: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_65: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_66: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_67: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_68: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_69: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_70: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_71: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_72: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_73: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_74: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_75: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_76: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_77: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_78: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_79: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_80: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_81: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_82: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_83: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_84: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.blank_85: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu1_header.end: END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header. - hdu2_header: Header of HDU 2, an image extension (EXTNAME 'SCI'), a 270 x 263 array: The header of HDU 2, an image extension (EXTNAME 'SCI'), a 270 x 263 array: 144 keyword records of 80 ASCII characters, the last END, in 4 blocks. - hdu2_header.xtension: XTENSION: The value field shall contain a character string giving the name of the extension type. This keyword is mandatory for an extension header and must not appear in the primary header.7 To preclude conflict, extension type names must be registered with the IAUFWG. The current list of registered extensions is given in Appendix F. An up-to-date list is also maintained on the FITS Support Office website. This record's comment: "Image extension" - hdu2_header.bitpix: BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two's complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record's comment: "Bits per pixel" - hdu2_header.naxis: NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record's comment: "Number of axes" - hdu2_header.naxis1: NAXIS1: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu2_header.naxis2: NAXIS2: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu2_header.pcount: PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record's comment: "No 'random' parameters" - hdu2_header.gcount: GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record's comment: "Only one group" - hdu2_header.origin: ORIGIN: The value field shall contain a character string identifying the organization or institution responsible for creating the FITS file. This record's comment: "FITS file originator" - hdu2_header.extname: EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record's comment: "Extension name" - hdu2_header.extver: EXTVER: The value field shall contain an integer to be used to distinguish among different extensions in a FITS file with the same type and name, i.e., the same values for XTENSION and EXTNAME. The values need not start with 1 for the first extension with a particular value of EXTNAME and need not be in sequence for subsequent values. If the EXTVER keyword is absent, the file should be treated as if the value were 1. This record's comment: "Extension version" - hdu2_header.date: DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record's comment: "Date FITS file was generated" - hdu2_header.iraf_tlm: IRAF-TLM: A keyword the FITS Standard doesn't define. This record's comment: "Time of last modification" - hdu2_header.datamin: DATAMIN: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the minimum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Minimum data value" - hdu2_header.datamax: DATAMAX: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the maximum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Maximum data value" - hdu2_header.inherit: INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record's comment: "inherit the primary header" - hdu2_header.expname: EXPNAME: A keyword the FITS Standard doesn't define. This record's comment: "exposure identifier" - hdu2_header.bunit: BUNIT: The value field shall contain a character string describing the physical units in which the quantities in the array, after application of BSCALE and BZERO, are expressed. These units must follow the prescriptions of Sect. 4.3. This record's comment: "brightness units" - hdu2_header.blank: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_2: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_3: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.wcsaxes: WCSAXES: Number of axes in the WCS description. This keyword, if present, must precede all WCS keywords except NAXIS in the HDU. The value of WCSAXES may exceed the number of pixel axes for the HDU. This record's comment: "number of World Coordinate System axes" - hdu2_header.crpix1: CRPIX1: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "x-coordinate of reference pixel" - hdu2_header.crpix2: CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "y-coordinate of reference pixel" - hdu2_header.crval1: CRVAL1: World-coordinate value at the reference point of Axis i. This record's comment: "first axis value at reference pixel" - hdu2_header.crval2: CRVAL2: World-coordinate value at the reference point of Axis i. This record's comment: "second axis value at reference pixel" - hdu2_header.ctype1: CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the first axis" - hdu2_header.ctype2: CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the second axis" - hdu2_header.cd1_1: CD1_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. x" - hdu2_header.cd1_2: CD1_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. y" - hdu2_header.cd2_1: CD2_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. x" - hdu2_header.cd2_2: CD2_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. y" - hdu2_header.blank_4: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_5: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_6: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.fillcnt: FILLCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing fill" - hdu2_header.errcnt: ERRCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing errors" - hdu2_header.podpsff: PODPSFF: A keyword the FITS Standard doesn't define. This record's comment: "podps fill present (T/F)" - hdu2_header.stdcfff: STDCFFF: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill present (T/F)" - hdu2_header.stdcffp: STDCFFP: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill pattern (hex)" - hdu2_header.blank_7: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_8: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_9: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.sampnum: SAMPNUM: A keyword the FITS Standard doesn't define. This record's comment: "MULTIACCUM sample number" - hdu2_header.samptime: SAMPTIME: A keyword the FITS Standard doesn't define. This record's comment: "total integration time (sec)" - hdu2_header.deltatim: DELTATIM: A keyword the FITS Standard doesn't define. This record's comment: "integration time of this sample (sec)" - hdu2_header.routtime: ROUTTIME: A keyword the FITS Standard doesn't define. This record's comment: "UT time of array readout (MJD)" - hdu2_header.tdftrans: TDFTRANS: A keyword the FITS Standard doesn't define. This record's comment: "number of TDF transitions during current sample" - hdu2_header.blank_10: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_11: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_12: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.engqual: ENGQUAL: A keyword the FITS Standard doesn't define. This record's comment: "engineering quality (NORMAL, FLAGS)" - hdu2_header.nqual00: NQUAL00: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with all DQ flags equal zero" - hdu2_header.nqual01: NQUAL01: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Reed-Solomon flag" - hdu2_header.nqual02: NQUAL02: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with NonLinearity flag" - hdu2_header.nqual03: NQUAL03: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Dark flag set" - hdu2_header.nqual04: NQUAL04: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Flat Field flag set" - hdu2_header.nqual05: NQUAL05: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Grot flag set" - hdu2_header.nqual06: NQUAL06: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Defective flag set" - hdu2_header.nqual07: NQUAL07: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Saturated flag set" - hdu2_header.nqual08: NQUAL08: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Missing flag set" - hdu2_header.nqual09: NQUAL09: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Bad Pixel flag set" - hdu2_header.nqual10: NQUAL10: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Cosmic Ray flag set" - hdu2_header.nqual11: NQUAL11: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with Source flag set" - hdu2_header.nqual12: NQUAL12: A keyword the FITS Standard doesn't define. This record's comment: "number of pixels with ZeroRead Signal flag set" - hdu2_header.goodmean: GOODMEAN: A keyword the FITS Standard doesn't define. This record's comment: "mean of good pixels (no dq flags set)" - hdu2_header.goodmedn: GOODMEDN: A keyword the FITS Standard doesn't define. This record's comment: "median of good pixels" - hdu2_header.goodstdv: GOODSTDV: A keyword the FITS Standard doesn't define. This record's comment: "standard deviation of good pixels" - hdu2_header.goodmin: GOODMIN: A keyword the FITS Standard doesn't define. This record's comment: "minimum value of good pixels" - hdu2_header.goodmax: GOODMAX: A keyword the FITS Standard doesn't define. This record's comment: "maximum value of good pixels" - hdu2_header.qamean: QAMEAN: A keyword the FITS Standard doesn't define. This record's comment: "mean of good pixels in quadrant A" - hdu2_header.qamedn: QAMEDN: A keyword the FITS Standard doesn't define. This record's comment: "median of good pixels in quadrant A" - hdu2_header.qastdv: QASTDV: A keyword the FITS Standard doesn't define. This record's comment: "standard deviation of good pixels in quad A" - hdu2_header.qamin: QAMIN: A keyword the FITS Standard doesn't define. This record's comment: "min value of good pixels in quadrant A" - hdu2_header.qamax: QAMAX: A keyword the FITS Standard doesn't define. This record's comment: "max value of good pixels in quadrant A" - hdu2_header.qbmean: QBMEAN: A keyword the FITS Standard doesn't define. This record's comment: "mean of good pixels in quadrant B" - hdu2_header.qbmedn: QBMEDN: A keyword the FITS Standard doesn't define. This record's comment: "median of good pixels in quadrant B" - hdu2_header.qbstdv: QBSTDV: A keyword the FITS Standard doesn't define. This record's comment: "standard deviation of good pixels in quad B" - hdu2_header.qbmin: QBMIN: A keyword the FITS Standard doesn't define. This record's comment: "min value of good pixels in quadrant B" - hdu2_header.qbmax: QBMAX: A keyword the FITS Standard doesn't define. This record's comment: "max value of good pixels in quadrant B" - hdu2_header.qcmean: QCMEAN: A keyword the FITS Standard doesn't define. This record's comment: "mean of good pixels in quadrant C" - hdu2_header.qcmedn: QCMEDN: A keyword the FITS Standard doesn't define. This record's comment: "median of good pixels in quadrant C" - hdu2_header.qcstdv: QCSTDV: A keyword the FITS Standard doesn't define. This record's comment: "standard deviation of good pixels in quad C" - hdu2_header.qcmin: QCMIN: A keyword the FITS Standard doesn't define. This record's comment: "min value of good pixels in quadrant C" - hdu2_header.qcmax: QCMAX: A keyword the FITS Standard doesn't define. This record's comment: "max value of good pixels in quadrant C" - hdu2_header.qdmean: QDMEAN: A keyword the FITS Standard doesn't define. This record's comment: "mean of good pixels in quadrant D" - hdu2_header.qdmedn: QDMEDN: A keyword the FITS Standard doesn't define. This record's comment: "median of good pixels in quadrant D" - hdu2_header.qdstdv: QDSTDV: A keyword the FITS Standard doesn't define. This record's comment: "standard deviation of good pixels in quad D" - hdu2_header.qdmin: QDMIN: A keyword the FITS Standard doesn't define. This record's comment: "min value of good pixels in quadrant D" - hdu2_header.qdmax: QDMAX: A keyword the FITS Standard doesn't define. This record's comment: "max value of good pixels in quadrant D" - hdu2_header.history: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_2: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_3: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_4: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_5: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_6: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_7: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_8: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_9: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_10: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_11: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_12: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_13: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_14: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_15: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_16: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_17: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_18: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_19: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_20: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_21: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_22: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_23: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_24: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_25: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_26: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_27: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_28: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_29: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_30: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_31: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_32: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_33: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_34: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.history_35: HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80. - hdu2_header.rootname: ROOTNAME: A keyword the FITS Standard doesn't define. - hdu2_header.blank_13: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_14: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_15: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_16: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_17: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_18: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_19: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_20: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_21: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_22: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_23: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_24: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_25: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_26: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_27: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_28: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_29: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.blank_30: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu2_header.end: END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header. - hdu2_image: Image row: One row of the 270 x 263 array of HDU 2, an image extension (EXTNAME 'SCI'), a 270 x 263 array: 270 pixels along axis 1. - hdu2_image.pixel: Pixel value (COUNTS/S): The values of the 270 x 263 array of HDU 2, an image extension (EXTNAME 'SCI'), a 270 x 263 array, IEEE single-precision floating point (BITPIX = -32), one row of 270 values per "hdu2_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN. - hdu3_header: Header of HDU 3, an image extension (EXTNAME 'ERR'), a 270 x 263 array: The header of HDU 3, an image extension (EXTNAME 'ERR'), a 270 x 263 array: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks. - hdu3_header.xtension: XTENSION: The value field shall contain a character string giving the name of the extension type. This keyword is mandatory for an extension header and must not appear in the primary header.7 To preclude conflict, extension type names must be registered with the IAUFWG. The current list of registered extensions is given in Appendix F. An up-to-date list is also maintained on the FITS Support Office website. This record's comment: "Image extension" - hdu3_header.bitpix: BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two's complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record's comment: "Bits per pixel" - hdu3_header.naxis: NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record's comment: "Number of axes" - hdu3_header.naxis1: NAXIS1: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu3_header.naxis2: NAXIS2: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu3_header.pcount: PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record's comment: "No 'random' parameters" - hdu3_header.gcount: GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record's comment: "Only one group" - hdu3_header.origin: ORIGIN: The value field shall contain a character string identifying the organization or institution responsible for creating the FITS file. This record's comment: "FITS file originator" - hdu3_header.extname: EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record's comment: "Extension name" - hdu3_header.extver: EXTVER: The value field shall contain an integer to be used to distinguish among different extensions in a FITS file with the same type and name, i.e., the same values for XTENSION and EXTNAME. The values need not start with 1 for the first extension with a particular value of EXTNAME and need not be in sequence for subsequent values. If the EXTVER keyword is absent, the file should be treated as if the value were 1. This record's comment: "Extension version" - hdu3_header.date: DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record's comment: "Date FITS file was generated" - hdu3_header.iraf_tlm: IRAF-TLM: A keyword the FITS Standard doesn't define. This record's comment: "Time of last modification" - hdu3_header.datamin: DATAMIN: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the minimum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Minimum data value" - hdu3_header.datamax: DATAMAX: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the maximum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Maximum data value" - hdu3_header.inherit: INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record's comment: "inherit the primary header" - hdu3_header.expname: EXPNAME: A keyword the FITS Standard doesn't define. This record's comment: "exposure identifier" - hdu3_header.bunit: BUNIT: The value field shall contain a character string describing the physical units in which the quantities in the array, after application of BSCALE and BZERO, are expressed. These units must follow the prescriptions of Sect. 4.3. This record's comment: "brightness units" - hdu3_header.blank: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_2: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_3: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.wcsaxes: WCSAXES: Number of axes in the WCS description. This keyword, if present, must precede all WCS keywords except NAXIS in the HDU. The value of WCSAXES may exceed the number of pixel axes for the HDU. This record's comment: "number of World Coordinate System axes" - hdu3_header.crpix1: CRPIX1: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "x-coordinate of reference pixel" - hdu3_header.crpix2: CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "y-coordinate of reference pixel" - hdu3_header.crval1: CRVAL1: World-coordinate value at the reference point of Axis i. This record's comment: "first axis value at reference pixel" - hdu3_header.crval2: CRVAL2: World-coordinate value at the reference point of Axis i. This record's comment: "second axis value at reference pixel" - hdu3_header.ctype1: CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the first axis" - hdu3_header.ctype2: CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the second axis" - hdu3_header.cd1_1: CD1_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. x" - hdu3_header.cd1_2: CD1_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. y" - hdu3_header.cd2_1: CD2_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. x" - hdu3_header.cd2_2: CD2_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. y" - hdu3_header.blank_4: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_5: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_6: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.fillcnt: FILLCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing fill" - hdu3_header.errcnt: ERRCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing errors" - hdu3_header.podpsff: PODPSFF: A keyword the FITS Standard doesn't define. This record's comment: "podps fill present (T/F)" - hdu3_header.stdcfff: STDCFFF: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill present (T/F)" - hdu3_header.stdcffp: STDCFFP: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill pattern (hex)" - hdu3_header.rootname: ROOTNAME: A keyword the FITS Standard doesn't define. - hdu3_header.blank_7: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_8: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_9: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_10: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_11: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_12: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_13: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_14: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_15: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_16: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_17: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_18: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_19: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_20: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_21: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_22: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_23: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_24: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_25: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_26: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_27: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_28: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_29: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_30: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_31: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_32: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_33: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_34: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_35: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_36: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.blank_37: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu3_header.end: END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header. - hdu3_image: Image row: One row of the 270 x 263 array of HDU 3, an image extension (EXTNAME 'ERR'), a 270 x 263 array: 270 pixels along axis 1. - hdu3_image.pixel: Pixel value (COUNTS/S): The values of the 270 x 263 array of HDU 3, an image extension (EXTNAME 'ERR'), a 270 x 263 array, IEEE single-precision floating point (BITPIX = -32), one row of 270 values per "hdu3_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN. - hdu4_header: Header of HDU 4, an image extension (EXTNAME 'DQ'), a 270 x 263 array: The header of HDU 4, an image extension (EXTNAME 'DQ'), a 270 x 263 array: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks. - hdu4_header.xtension: XTENSION: The value field shall contain a character string giving the name of the extension type. This keyword is mandatory for an extension header and must not appear in the primary header.7 To preclude conflict, extension type names must be registered with the IAUFWG. The current list of registered extensions is given in Appendix F. An up-to-date list is also maintained on the FITS Support Office website. This record's comment: "Image extension" - hdu4_header.bitpix: BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two's complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record's comment: "Bits per pixel" - hdu4_header.naxis: NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record's comment: "Number of axes" - hdu4_header.naxis1: NAXIS1: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu4_header.naxis2: NAXIS2: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu4_header.pcount: PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record's comment: "No 'random' parameters" - hdu4_header.gcount: GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record's comment: "Only one group" - hdu4_header.origin: ORIGIN: The value field shall contain a character string identifying the organization or institution responsible for creating the FITS file. This record's comment: "FITS file originator" - hdu4_header.extname: EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record's comment: "Extension name" - hdu4_header.extver: EXTVER: The value field shall contain an integer to be used to distinguish among different extensions in a FITS file with the same type and name, i.e., the same values for XTENSION and EXTNAME. The values need not start with 1 for the first extension with a particular value of EXTNAME and need not be in sequence for subsequent values. If the EXTVER keyword is absent, the file should be treated as if the value were 1. This record's comment: "Extension version" - hdu4_header.date: DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record's comment: "Date FITS file was generated" - hdu4_header.iraf_tlm: IRAF-TLM: A keyword the FITS Standard doesn't define. This record's comment: "Time of last modification" - hdu4_header.datamin: DATAMIN: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the minimum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Minimum data value" - hdu4_header.datamax: DATAMAX: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the maximum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Maximum data value" - hdu4_header.inherit: INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record's comment: "inherit the primary header" - hdu4_header.expname: EXPNAME: A keyword the FITS Standard doesn't define. This record's comment: "exposure identifier" - hdu4_header.bunit: BUNIT: The value field shall contain a character string describing the physical units in which the quantities in the array, after application of BSCALE and BZERO, are expressed. These units must follow the prescriptions of Sect. 4.3. This record's comment: "brightness units" - hdu4_header.blank: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_2: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_3: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.wcsaxes: WCSAXES: Number of axes in the WCS description. This keyword, if present, must precede all WCS keywords except NAXIS in the HDU. The value of WCSAXES may exceed the number of pixel axes for the HDU. This record's comment: "number of World Coordinate System axes" - hdu4_header.crpix1: CRPIX1: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "x-coordinate of reference pixel" - hdu4_header.crpix2: CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "y-coordinate of reference pixel" - hdu4_header.crval1: CRVAL1: World-coordinate value at the reference point of Axis i. This record's comment: "first axis value at reference pixel" - hdu4_header.crval2: CRVAL2: World-coordinate value at the reference point of Axis i. This record's comment: "second axis value at reference pixel" - hdu4_header.ctype1: CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the first axis" - hdu4_header.ctype2: CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the second axis" - hdu4_header.cd1_1: CD1_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. x" - hdu4_header.cd1_2: CD1_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. y" - hdu4_header.cd2_1: CD2_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. x" - hdu4_header.cd2_2: CD2_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. y" - hdu4_header.blank_4: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_5: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_6: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.fillcnt: FILLCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing fill" - hdu4_header.errcnt: ERRCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing errors" - hdu4_header.podpsff: PODPSFF: A keyword the FITS Standard doesn't define. This record's comment: "podps fill present (T/F)" - hdu4_header.stdcfff: STDCFFF: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill present (T/F)" - hdu4_header.stdcffp: STDCFFP: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill pattern (hex)" - hdu4_header.rootname: ROOTNAME: A keyword the FITS Standard doesn't define. - hdu4_header.blank_7: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_8: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_9: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_10: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_11: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_12: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_13: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_14: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_15: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_16: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_17: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_18: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_19: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_20: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_21: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_22: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_23: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_24: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_25: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_26: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_27: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_28: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_29: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_30: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_31: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_32: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_33: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_34: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_35: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_36: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.blank_37: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu4_header.end: END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header. - hdu4_image: Image row: One row of the 270 x 263 array of HDU 4, an image extension (EXTNAME 'DQ'), a 270 x 263 array: 270 pixels along axis 1. - hdu4_image.pixel: Pixel value (UNITLESS): The values of the 270 x 263 array of HDU 4, an image extension (EXTNAME 'DQ'), a 270 x 263 array, 16-bit two's complement integers (BITPIX = 16), one row of 270 values per "hdu4_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN. - hdu5_header: Header of HDU 5, an image extension (EXTNAME 'SAMP'), a 270 x 263 array: The header of HDU 5, an image extension (EXTNAME 'SAMP'), a 270 x 263 array: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks. - hdu5_header.xtension: XTENSION: The value field shall contain a character string giving the name of the extension type. This keyword is mandatory for an extension header and must not appear in the primary header.7 To preclude conflict, extension type names must be registered with the IAUFWG. The current list of registered extensions is given in Appendix F. An up-to-date list is also maintained on the FITS Support Office website. This record's comment: "Image extension" - hdu5_header.bitpix: BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two's complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record's comment: "Bits per pixel" - hdu5_header.naxis: NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record's comment: "Number of axes" - hdu5_header.naxis1: NAXIS1: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu5_header.naxis2: NAXIS2: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu5_header.pcount: PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record's comment: "No 'random' parameters" - hdu5_header.gcount: GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record's comment: "Only one group" - hdu5_header.origin: ORIGIN: The value field shall contain a character string identifying the organization or institution responsible for creating the FITS file. This record's comment: "FITS file originator" - hdu5_header.extname: EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record's comment: "Extension name" - hdu5_header.extver: EXTVER: The value field shall contain an integer to be used to distinguish among different extensions in a FITS file with the same type and name, i.e., the same values for XTENSION and EXTNAME. The values need not start with 1 for the first extension with a particular value of EXTNAME and need not be in sequence for subsequent values. If the EXTVER keyword is absent, the file should be treated as if the value were 1. This record's comment: "Extension version" - hdu5_header.date: DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record's comment: "Date FITS file was generated" - hdu5_header.iraf_tlm: IRAF-TLM: A keyword the FITS Standard doesn't define. This record's comment: "Time of last modification" - hdu5_header.datamin: DATAMIN: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the minimum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Minimum data value" - hdu5_header.datamax: DATAMAX: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the maximum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Maximum data value" - hdu5_header.inherit: INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record's comment: "inherit the primary header" - hdu5_header.expname: EXPNAME: A keyword the FITS Standard doesn't define. This record's comment: "exposure identifier" - hdu5_header.bunit: BUNIT: The value field shall contain a character string describing the physical units in which the quantities in the array, after application of BSCALE and BZERO, are expressed. These units must follow the prescriptions of Sect. 4.3. This record's comment: "brightness units" - hdu5_header.blank: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_2: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_3: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.wcsaxes: WCSAXES: Number of axes in the WCS description. This keyword, if present, must precede all WCS keywords except NAXIS in the HDU. The value of WCSAXES may exceed the number of pixel axes for the HDU. This record's comment: "number of World Coordinate System axes" - hdu5_header.crpix1: CRPIX1: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "x-coordinate of reference pixel" - hdu5_header.crpix2: CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "y-coordinate of reference pixel" - hdu5_header.crval1: CRVAL1: World-coordinate value at the reference point of Axis i. This record's comment: "first axis value at reference pixel" - hdu5_header.crval2: CRVAL2: World-coordinate value at the reference point of Axis i. This record's comment: "second axis value at reference pixel" - hdu5_header.ctype1: CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the first axis" - hdu5_header.ctype2: CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the second axis" - hdu5_header.cd1_1: CD1_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. x" - hdu5_header.cd1_2: CD1_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. y" - hdu5_header.cd2_1: CD2_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. x" - hdu5_header.cd2_2: CD2_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. y" - hdu5_header.blank_4: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_5: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_6: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.fillcnt: FILLCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing fill" - hdu5_header.errcnt: ERRCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing errors" - hdu5_header.podpsff: PODPSFF: A keyword the FITS Standard doesn't define. This record's comment: "podps fill present (T/F)" - hdu5_header.stdcfff: STDCFFF: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill present (T/F)" - hdu5_header.stdcffp: STDCFFP: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill pattern (hex)" - hdu5_header.rootname: ROOTNAME: A keyword the FITS Standard doesn't define. - hdu5_header.blank_7: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_8: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_9: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_10: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_11: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_12: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_13: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_14: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_15: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_16: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_17: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_18: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_19: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_20: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_21: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_22: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_23: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_24: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_25: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_26: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_27: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_28: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_29: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_30: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_31: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_32: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_33: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_34: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_35: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_36: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.blank_37: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu5_header.end: END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header. - hdu5_image: Image row: One row of the 270 x 263 array of HDU 5, an image extension (EXTNAME 'SAMP'), a 270 x 263 array: 270 pixels along axis 1. - hdu5_image.pixel: Pixel value (SAMPLES): The values of the 270 x 263 array of HDU 5, an image extension (EXTNAME 'SAMP'), a 270 x 263 array, 16-bit two's complement integers (BITPIX = 16), one row of 270 values per "hdu5_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN. - hdu6_header: Header of HDU 6, an image extension (EXTNAME 'TIME'), a 270 x 263 array: The header of HDU 6, an image extension (EXTNAME 'TIME'), a 270 x 263 array: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks. - hdu6_header.xtension: XTENSION: The value field shall contain a character string giving the name of the extension type. This keyword is mandatory for an extension header and must not appear in the primary header.7 To preclude conflict, extension type names must be registered with the IAUFWG. The current list of registered extensions is given in Appendix F. An up-to-date list is also maintained on the FITS Support Office website. This record's comment: "Image extension" - hdu6_header.bitpix: BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two's complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record's comment: "Bits per pixel" - hdu6_header.naxis: NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record's comment: "Number of axes" - hdu6_header.naxis1: NAXIS1: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu6_header.naxis2: NAXIS2: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record's comment: "Axis length" - hdu6_header.pcount: PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record's comment: "No 'random' parameters" - hdu6_header.gcount: GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record's comment: "Only one group" - hdu6_header.origin: ORIGIN: The value field shall contain a character string identifying the organization or institution responsible for creating the FITS file. This record's comment: "FITS file originator" - hdu6_header.extname: EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record's comment: "Extension name" - hdu6_header.extver: EXTVER: The value field shall contain an integer to be used to distinguish among different extensions in a FITS file with the same type and name, i.e., the same values for XTENSION and EXTNAME. The values need not start with 1 for the first extension with a particular value of EXTNAME and need not be in sequence for subsequent values. If the EXTVER keyword is absent, the file should be treated as if the value were 1. This record's comment: "Extension version" - hdu6_header.date: DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record's comment: "Date FITS file was generated" - hdu6_header.iraf_tlm: IRAF-TLM: A keyword the FITS Standard doesn't define. This record's comment: "Time of last modification" - hdu6_header.datamin: DATAMIN: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the minimum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Minimum data value" - hdu6_header.datamax: DATAMAX: The value field shall always contain a floating-point number, regardless of the value of BITPIX. This number shall give the maximum valid physical value represented by the array (from Eq. 3), exclusive of any IEEE special values. This record's comment: "Maximum data value" - hdu6_header.inherit: INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record's comment: "inherit the primary header" - hdu6_header.expname: EXPNAME: A keyword the FITS Standard doesn't define. This record's comment: "exposure identifier" - hdu6_header.bunit: BUNIT: The value field shall contain a character string describing the physical units in which the quantities in the array, after application of BSCALE and BZERO, are expressed. These units must follow the prescriptions of Sect. 4.3. This record's comment: "brightness units" - hdu6_header.blank: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_2: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_3: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.wcsaxes: WCSAXES: Number of axes in the WCS description. This keyword, if present, must precede all WCS keywords except NAXIS in the HDU. The value of WCSAXES may exceed the number of pixel axes for the HDU. This record's comment: "number of World Coordinate System axes" - hdu6_header.crpix1: CRPIX1: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "x-coordinate of reference pixel" - hdu6_header.crpix2: CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record's comment: "y-coordinate of reference pixel" - hdu6_header.crval1: CRVAL1: World-coordinate value at the reference point of Axis i. This record's comment: "first axis value at reference pixel" - hdu6_header.crval2: CRVAL2: World-coordinate value at the reference point of Axis i. This record's comment: "second axis value at reference pixel" - hdu6_header.ctype1: CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the first axis" - hdu6_header.ctype2: CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record's comment: "the coordinate type for the second axis" - hdu6_header.cd1_1: CD1_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. x" - hdu6_header.cd1_2: CD1_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of first axis coordinate w.r.t. y" - hdu6_header.cd2_1: CD2_1: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. x" - hdu6_header.cd2_2: CD2_2: Linear transformation matrix (with scale) between Pixel Axes j and Intermediate-coordinate Axes i. This nomenclature is used in place of PCi_j and CDELTi, combining the rotation and the scale. This record's comment: "partial of second axis coordinate w.r.t. y" - hdu6_header.blank_4: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_5: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_6: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.fillcnt: FILLCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing fill" - hdu6_header.errcnt: ERRCNT: A keyword the FITS Standard doesn't define. This record's comment: "number of segments containing errors" - hdu6_header.podpsff: PODPSFF: A keyword the FITS Standard doesn't define. This record's comment: "podps fill present (T/F)" - hdu6_header.stdcfff: STDCFFF: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill present (T/F)" - hdu6_header.stdcffp: STDCFFP: A keyword the FITS Standard doesn't define. This record's comment: "ST DDF fill pattern (hex)" - hdu6_header.rootname: ROOTNAME: A keyword the FITS Standard doesn't define. - hdu6_header.blank_7: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_8: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_9: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_10: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_11: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_12: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_13: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_14: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_15: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_16: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_17: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_18: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_19: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_20: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_21: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_22: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_23: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_24: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_25: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_26: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_27: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_28: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_29: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_30: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_31: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_32: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_33: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_34: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_35: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_36: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.blank_37: (blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill. - hdu6_header.end: END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header. - hdu6_image: Image row: One row of the 270 x 263 array of HDU 6, an image extension (EXTNAME 'TIME'), a 270 x 263 array: 270 pixels along axis 1. - hdu6_image.pixel: Pixel value (SECONDS): The values of the 270 x 263 array of HDU 6, an image extension (EXTNAME 'TIME'), a 270 x 263 array, IEEE single-precision floating point (BITPIX = -32), one row of 270 values per "hdu6_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN. |
| label | Semantics of FITS file NICMOSn4hk12010_mos.fits |
Links to
- interpretedUsingRecurse → FITS keyword dictionary (FITS Standard 4.0)
- interpretedUsingRecurse → Header of HDU 1, the primary HDU, with no data
- interpretedUsingRecurse → Header of HDU 2, an image extension (EXTNAME 'SCI'), a 270 x 263 array
- interpretedUsingRecurse → Header of HDU 3, an image extension (EXTNAME 'ERR'), a 270 x 263 array
- interpretedUsingRecurse → Header of HDU 4, an image extension (EXTNAME 'DQ'), a 270 x 263 array
- interpretedUsingRecurse → Header of HDU 5, an image extension (EXTNAME 'SAMP'), a 270 x 263 array
- interpretedUsingRecurse → Header of HDU 6, an image extension (EXTNAME 'TIME'), a 270 x 263 array
- interpretedUsingRecurse → Image row
- interpretedUsingRecurse → Image row
- interpretedUsingRecurse → Image row
- interpretedUsingRecurse → Image row
- interpretedUsingRecurse → Image row
- interpretedUsingRecurse → Image view of FITS file NICMOSn4hk12010_mos.fits
Linked from
- Representation Information for FITS file NICMOSn4hk12010_mos.fits → hasGroupMember
- Representation Information for FITS file NICMOSn4hk12010_mos.fits → hasSemanticRepresentationInformation