FITS file WFPC2ASSNu5780205bx.fits: Kaitai Struct description

StructureRepresentationInformation · http://example.org/archive/structure-representation-information-a1b6b1e2

View in graph → Edit →

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 Byte layout of "FITS file WFPC2ASSNu5780205bx.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file WFPC2ASSNu5780205bx.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_wfpc2_assnu5780205bx_fits' endian: be encoding: ASCII doc: 'Described from its headers, by archive-manager''s RepInfo Tools (FITS Standard 4.0, https://fits.gsfc.nasa.gov/fits_standard.html): 1 HDU. hdu1: HDU 1, the primary HDU, a 100 x 100 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.' seq: - id: 'hdu1_header' type: 'hdu1_header' doc: 'Header of HDU 1, the primary HDU, a 100 x 100 array: The header of HDU 1, the primary HDU, a 100 x 100 array: 258 keyword records of 80 ASCII characters, the last END, in 8 blocks.' - id: 'hdu1_image' type: 'hdu1_image' repeat: expr repeat-expr: 100 doc: 'Image row: One row of the 100 x 100 array of HDU 1, the primary HDU, a 100 x 100 array: 100 pixels along axis 1.' - id: 'hdu1_fill' size: 320 doc: 'Fill: Fill after the data of HDU 1, the primary HDU, a 100 x 100 array, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, a 100 x 100 array: The header of HDU 1, the primary HDU, a 100 x 100 array: 258 keyword records of 80 ASCII characters, the last END, in 8 blocks.' seq: - id: 'simple' type: str size: 80 doc: '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: "file does conform to FITS standard"' doc-ref: 'http://ontology.oais.info/fits/keyword/SIMPLE' - id: 'bitpix' type: str size: 80 doc: '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: "number of bits per data pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/BITPIX' - id: 'naxis' type: str size: 80 doc: '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 data axes"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXIS' - id: 'naxis1' type: str size: 80 doc: '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: "length of data axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'naxis2' type: str size: 80 doc: '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: "length of data axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'extend' type: str size: 80 doc: '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: "FITS dataset may contain extensions"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTEND' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'origin' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'date' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE' - id: 'iraf_tlm' type: str size: 80 doc: 'IRAF-TLM: A keyword the FITS Standard doesn''t define. This record''s comment: "Time of last modification"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of the object observed"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'crval1' type: str size: 80 doc: 'CRVAL1: World-coordinate value at the reference point of Axis i.' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'crval2' type: str size: 80 doc: 'CRVAL2: World-coordinate value at the reference point of Axis i.' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'crpix1' type: str size: 80 doc: '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, . . .).' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'crpix2' type: str size: 80 doc: '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, . . .).' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'cd1_1' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDi_j' - id: 'cd1_2' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDi_j' - id: 'cd2_1' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDi_j' - id: 'cd2_2' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDi_j' - id: 'mir_revr' type: str size: 80 doc: 'MIR_REVR: A keyword the FITS Standard doesn''t define.' - id: 'orientat' type: str size: 80 doc: 'ORIENTAT: A keyword the FITS Standard doesn''t define.' - id: 'fillcnt' type: str size: 80 doc: 'FILLCNT: A keyword the FITS Standard doesn''t define.' - id: 'errcnt' type: str size: 80 doc: 'ERRCNT: A keyword the FITS Standard doesn''t define.' - id: 'fpkttime' type: str size: 80 doc: 'FPKTTIME: A keyword the FITS Standard doesn''t define.' - id: 'lpkttime' type: str size: 80 doc: 'LPKTTIME: A keyword the FITS Standard doesn''t define.' - id: 'ctype1' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'ctype2' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'detector' type: str size: 80 doc: 'DETECTOR: A keyword the FITS Standard doesn''t define.' - id: 'dezero' type: str size: 80 doc: 'DEZERO: A keyword the FITS Standard doesn''t define.' - id: 'biaseven' type: str size: 80 doc: 'BIASEVEN: A keyword the FITS Standard doesn''t define.' - id: 'biasodd' type: str size: 80 doc: 'BIASODD: A keyword the FITS Standard doesn''t define.' - id: 'goodmin' type: str size: 80 doc: 'GOODMIN: A keyword the FITS Standard doesn''t define.' - id: 'goodmax' type: str size: 80 doc: 'GOODMAX: A keyword the FITS Standard doesn''t define.' - id: 'datamean' type: str size: 80 doc: 'DATAMEAN: A keyword the FITS Standard doesn''t define.' - id: 'gpixels' type: str size: 80 doc: 'GPIXELS: A keyword the FITS Standard doesn''t define.' - id: 'softerrs' type: str size: 80 doc: 'SOFTERRS: A keyword the FITS Standard doesn''t define.' - id: 'calibdef' type: str size: 80 doc: 'CALIBDEF: A keyword the FITS Standard doesn''t define.' - id: 'staticd' type: str size: 80 doc: 'STATICD: A keyword the FITS Standard doesn''t define.' - id: 'atodsat' type: str size: 80 doc: 'ATODSAT: A keyword the FITS Standard doesn''t define.' - id: 'datalost' type: str size: 80 doc: 'DATALOST: A keyword the FITS Standard doesn''t define.' - id: 'badpixel' type: str size: 80 doc: 'BADPIXEL: A keyword the FITS Standard doesn''t define.' - id: 'overlap' type: str size: 80 doc: 'OVERLAP: A keyword the FITS Standard doesn''t define.' - id: 'photmode' type: str size: 80 doc: 'PHOTMODE: A keyword the FITS Standard doesn''t define.' - id: 'photflam' type: str size: 80 doc: 'PHOTFLAM: A keyword the FITS Standard doesn''t define.' - id: 'photzpt' type: str size: 80 doc: 'PHOTZPT: A keyword the FITS Standard doesn''t define.' - id: 'photplam' type: str size: 80 doc: 'PHOTPLAM: A keyword the FITS Standard doesn''t define.' - id: 'photbw' type: str size: 80 doc: 'PHOTBW: A keyword the FITS Standard doesn''t define.' - id: 'median' type: str size: 80 doc: 'MEDIAN: A keyword the FITS Standard doesn''t define.' - id: 'medshado' type: str size: 80 doc: 'MEDSHADO: A keyword the FITS Standard doesn''t define.' - id: 'histwide' type: str size: 80 doc: 'HISTWIDE: A keyword the FITS Standard doesn''t define.' - id: 'skewness' type: str size: 80 doc: 'SKEWNESS: A keyword the FITS Standard doesn''t define.' - id: 'meanc10' type: str size: 80 doc: 'MEANC10: A keyword the FITS Standard doesn''t define.' - id: 'meanc25' type: str size: 80 doc: 'MEANC25: A keyword the FITS Standard doesn''t define.' - id: 'meanc50' type: str size: 80 doc: 'MEANC50: A keyword the FITS Standard doesn''t define.' - id: 'meanc100' type: str size: 80 doc: 'MEANC100: A keyword the FITS Standard doesn''t define.' - id: 'meanc200' type: str size: 80 doc: 'MEANC200: A keyword the FITS Standard doesn''t define.' - id: 'meanc300' type: str size: 80 doc: 'MEANC300: A keyword the FITS Standard doesn''t define.' - id: 'backgrnd' type: str size: 80 doc: 'BACKGRND: A keyword the FITS Standard doesn''t define.' - id: 'filetype' type: str size: 80 doc: 'FILETYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "type of data found in data file"' - id: 'blank' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'telescop' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'instrume' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'equinox' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'blank_2' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_3' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_4' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'rootname' type: str size: 80 doc: 'ROOTNAME: A keyword the FITS Standard doesn''t define. This record''s comment: "rootname of the observation set"' - id: 'proctime' type: str size: 80 doc: 'PROCTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Pipeline processing time (MJD)"' - id: 'opus_ver' type: str size: 80 doc: 'OPUS_VER: A keyword the FITS Standard doesn''t define. This record''s comment: "OPUS software system version number"' - id: 'cal_ver' type: str size: 80 doc: 'CAL_VER: A keyword the FITS Standard doesn''t define. This record''s comment: "CALWP2 code version"' - id: 'blank_5' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_6' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_7' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'mode' type: str size: 80 doc: 'MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "instr. mode: FULL (full res.), AREA (area int.)"' - id: 'serials' type: str size: 80 doc: 'SERIALS: A keyword the FITS Standard doesn''t define. This record''s comment: "serial clocks: ON, OFF"' - id: 'blank_8' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_9' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_10' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'imagetyp' type: str size: 80 doc: 'IMAGETYP: A keyword the FITS Standard doesn''t define. This record''s comment: "DARK/BIAS/IFLAT/UFLAT/VFLAT/KSPOT/EXT/ECAL"' - id: 'cdbsfile' type: str size: 80 doc: 'CDBSFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "GENERIC/BIAS/DARK/PREF/FLAT/MASK/ATOD/NO"' - id: 'pktfmt' type: str size: 80 doc: 'PKTFMT: A keyword the FITS Standard doesn''t define. This record''s comment: "packet format code"' - id: 'blank_11' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_12' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_13' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'filtnam1' type: str size: 80 doc: 'FILTNAM1: A keyword the FITS Standard doesn''t define. This record''s comment: "first filter name"' - id: 'filtnam2' type: str size: 80 doc: 'FILTNAM2: A keyword the FITS Standard doesn''t define. This record''s comment: "second filter name"' - id: 'filter1' type: str size: 80 doc: 'FILTER1: A keyword the FITS Standard doesn''t define. This record''s comment: "first filter number (0-48)"' - id: 'filter2' type: str size: 80 doc: 'FILTER2: A keyword the FITS Standard doesn''t define. This record''s comment: "second filter number (0-48)"' - id: 'filtrot' type: str size: 80 doc: 'FILTROT: A keyword the FITS Standard doesn''t define. This record''s comment: "partial filter rotation angle (degrees)"' - id: 'lrfwave' type: str size: 80 doc: 'LRFWAVE: A keyword the FITS Standard doesn''t define. This record''s comment: "linear ramp filter wavelength"' - id: 'blank_14' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_15' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_16' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'uch1cjtm' type: str size: 80 doc: 'UCH1CJTM: A keyword the FITS Standard doesn''t define. This record''s comment: "TEC cold junction #1 temperature (Celsius)"' - id: 'uch2cjtm' type: str size: 80 doc: 'UCH2CJTM: A keyword the FITS Standard doesn''t define. This record''s comment: "TEC cold junction #2 temperature (Celsius)"' - id: 'uch3cjtm' type: str size: 80 doc: 'UCH3CJTM: A keyword the FITS Standard doesn''t define. This record''s comment: "TEC cold junction #3 temperature (Celsius)"' - id: 'uch4cjtm' type: str size: 80 doc: 'UCH4CJTM: A keyword the FITS Standard doesn''t define. This record''s comment: "TEC cold junction #4 temperature (Celsius)"' - id: 'ubay3tmp' type: str size: 80 doc: 'UBAY3TMP: A keyword the FITS Standard doesn''t define. This record''s comment: "bay 3 A1 temperature (deg C)"' - id: 'kspots' type: str size: 80 doc: 'KSPOTS: A keyword the FITS Standard doesn''t define. This record''s comment: "Status of Kelsall spot lamps: ON, OFF"' - id: 'shutter' type: str size: 80 doc: 'SHUTTER: A keyword the FITS Standard doesn''t define. This record''s comment: "Shutter in place at beginning of the exposure"' - id: 'atodgain' type: str size: 80 doc: 'ATODGAIN: A keyword the FITS Standard doesn''t define. This record''s comment: "Analog to Digital Gain (Electrons/DN)"' - id: 'blank_17' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_18' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_19' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'maskcorr' type: str size: 80 doc: 'MASKCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do mask correction: PERFORM, OMIT, COMPLETE"' - id: 'atodcorr' type: str size: 80 doc: 'ATODCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do A-to-D correction: PERFORM, OMIT, COMPLETE"' - id: 'blevcorr' type: str size: 80 doc: 'BLEVCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do bias level correction"' - id: 'biascorr' type: str size: 80 doc: 'BIASCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do bias correction: PERFORM, OMIT, COMPLETE"' - id: 'darkcorr' type: str size: 80 doc: 'DARKCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do dark correction: PERFORM, OMIT, COMPLETE"' - id: 'flatcorr' type: str size: 80 doc: 'FLATCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do flat field correction"' - id: 'shadcorr' type: str size: 80 doc: 'SHADCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "Do shaded shutter correction"' - id: 'dosatmap' type: str size: 80 doc: 'DOSATMAP: A keyword the FITS Standard doesn''t define. This record''s comment: "Output saturated pixel map"' - id: 'dophotom' type: str size: 80 doc: 'DOPHOTOM: A keyword the FITS Standard doesn''t define. This record''s comment: "Fill photometry keywords"' - id: 'dohistos' type: str size: 80 doc: 'DOHISTOS: A keyword the FITS Standard doesn''t define. This record''s comment: "Make histograms: PERFORM, OMIT, COMPLETE"' - id: 'outdtype' type: str size: 80 doc: 'OUTDTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Output image datatype: REAL, LONG, SHORT"' - id: 'blank_20' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_21' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_22' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'maskfile' type: str size: 80 doc: 'MASKFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the input DQF of known bad pixels"' - id: 'atodfile' type: str size: 80 doc: 'ATODFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the A-to-D conversion file"' - id: 'blevfile' type: str size: 80 doc: 'BLEVFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "Engineering file with extended register da"' - id: 'blevdfil' type: str size: 80 doc: 'BLEVDFIL: A keyword the FITS Standard doesn''t define. This record''s comment: "Engineering file DQF"' - id: 'biasfile' type: str size: 80 doc: 'BIASFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the bias frame reference file"' - id: 'biasdfil' type: str size: 80 doc: 'BIASDFIL: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the bias frame reference DQF"' - id: 'darkfile' type: str size: 80 doc: 'DARKFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the dark reference file"' - id: 'darkdfil' type: str size: 80 doc: 'DARKDFIL: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the dark reference DQF"' - id: 'flatfile' type: str size: 80 doc: 'FLATFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the flat field reference file"' - id: 'flatdfil' type: str size: 80 doc: 'FLATDFIL: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the flat field reference DQF"' - id: 'shadfile' type: str size: 80 doc: 'SHADFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the reference file for shutter sha"' - id: 'phottab' type: str size: 80 doc: 'PHOTTAB: A keyword the FITS Standard doesn''t define. This record''s comment: "name of the photometry calibration table"' - id: 'graphtab' type: str size: 80 doc: 'GRAPHTAB: A keyword the FITS Standard doesn''t define. This record''s comment: "the HST graph table"' - id: 'comptab' type: str size: 80 doc: 'COMPTAB: A keyword the FITS Standard doesn''t define. This record''s comment: "the HST components table"' - id: 'blank_23' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_24' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_25' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'saturate' type: str size: 80 doc: 'SATURATE: A keyword the FITS Standard doesn''t define. This record''s comment: "Data value at which saturation occurs"' - id: 'uscale' type: str size: 80 doc: 'USCALE: A keyword the FITS Standard doesn''t define. This record''s comment: "Scale factor for output image"' - id: 'uzero' type: str size: 80 doc: 'UZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "Zero point for output image"' - id: 'blank_26' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_27' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_28' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'readtime' type: str size: 80 doc: 'READTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Length of time for CCD readout in clock ticks"' - id: 'blank_29' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_30' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_31' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'pa_v3' type: str size: 80 doc: 'PA_V3: A keyword the FITS Standard doesn''t define. This record''s comment: "position angle of V3-axis of HST (deg)"' - id: 'ra_sun' type: str size: 80 doc: 'RA_SUN: A keyword the FITS Standard doesn''t define. This record''s comment: "right ascension of the sun (deg)"' - id: 'dec_sun' type: str size: 80 doc: 'DEC_SUN: A keyword the FITS Standard doesn''t define. This record''s comment: "declination of the sun (deg)"' - id: 'eqnx_sun' type: str size: 80 doc: 'EQNX_SUN: A keyword the FITS Standard doesn''t define. This record''s comment: "equinox of the sun"' - id: 'mtflag' type: str size: 80 doc: 'MTFLAG: A keyword the FITS Standard doesn''t define. This record''s comment: "moving target flag; T if it is a moving target"' - id: 'eqradtrg' type: str size: 80 doc: 'EQRADTRG: A keyword the FITS Standard doesn''t define. This record''s comment: "equatorial radius of target (km)"' - id: 'flatntrg' type: str size: 80 doc: 'FLATNTRG: A keyword the FITS Standard doesn''t define. This record''s comment: "flattening of target"' - id: 'npdectrg' type: str size: 80 doc: 'NPDECTRG: A keyword the FITS Standard doesn''t define. This record''s comment: "north pole declination of target (deg)"' - id: 'npratrg' type: str size: 80 doc: 'NPRATRG: A keyword the FITS Standard doesn''t define. This record''s comment: "north pole right ascension of target (deg)"' - id: 'rotrttrg' type: str size: 80 doc: 'ROTRTTRG: A keyword the FITS Standard doesn''t define. This record''s comment: "rotation rate of target"' - id: 'longpmer' type: str size: 80 doc: 'LONGPMER: A keyword the FITS Standard doesn''t define. This record''s comment: "longitude of prime meridian (deg)"' - id: 'eplongpm' type: str size: 80 doc: 'EPLONGPM: A keyword the FITS Standard doesn''t define. This record''s comment: "epoch of longitude of prime meridian (sec)"' - id: 'surflatd' type: str size: 80 doc: 'SURFLATD: A keyword the FITS Standard doesn''t define. This record''s comment: "surface feature latitude (deg)"' - id: 'surflong' type: str size: 80 doc: 'SURFLONG: A keyword the FITS Standard doesn''t define. This record''s comment: "surface feature longitude (deg)"' - id: 'surfaltd' type: str size: 80 doc: 'SURFALTD: A keyword the FITS Standard doesn''t define. This record''s comment: "surface feature altitude (km)"' - id: 'blank_32' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_33' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_34' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'podpsff' type: str size: 80 doc: 'PODPSFF: A keyword the FITS Standard doesn''t define. This record''s comment: "0=(no podps fill); 1=(podps fill present)"' - id: 'stdcfff' type: str size: 80 doc: 'STDCFFF: A keyword the FITS Standard doesn''t define. This record''s comment: "0=(no st dcf fill); 1=(st dcf fill present)"' - id: 'stdcffp' type: str size: 80 doc: 'STDCFFP: A keyword the FITS Standard doesn''t define. This record''s comment: "st dcf fill pattern (hex)"' - id: 'rsdpfill' type: str size: 80 doc: 'RSDPFILL: A keyword the FITS Standard doesn''t define. This record''s comment: "bad data fill value for calibrated images"' - id: 'blank_35' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_36' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_37' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'uexpodur' type: str size: 80 doc: 'UEXPODUR: A keyword the FITS Standard doesn''t define. This record''s comment: "commanded duration of exposure (sec)"' - id: 'nshuta17' type: str size: 80 doc: 'NSHUTA17: A keyword the FITS Standard doesn''t define. This record''s comment: "Number of AP17 shutter B closes"' - id: 'darktime' type: str size: 80 doc: 'DARKTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Dark time (seconds)"' - id: 'uexpotim' type: str size: 80 doc: 'UEXPOTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Major frame pulse time preceding exposure start"' - id: 'pstrtime' type: str size: 80 doc: 'PSTRTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "predicted obs. start time (yyyy.ddd:hh:mm:ss)"' - id: 'pstptime' type: str size: 80 doc: 'PSTPTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "predicted obs. stop time (yyyy.ddd:hh:mm:ss)"' - id: 'blank_38' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_39' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_40' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'sunangle' type: str size: 80 doc: 'SUNANGLE: A keyword the FITS Standard doesn''t define. This record''s comment: "angle between sun and V1 axis"' - id: 'moonangl' type: str size: 80 doc: 'MOONANGL: A keyword the FITS Standard doesn''t define. This record''s comment: "angle between moon and V1 axis"' - id: 'sun_alt' type: str size: 80 doc: 'SUN_ALT: A keyword the FITS Standard doesn''t define. This record''s comment: "altitude of the sun above Earth''s limb"' - id: 'fgslock' type: str size: 80 doc: 'FGSLOCK: A keyword the FITS Standard doesn''t define. This record''s comment: "commanded FGS lock (FINE,COARSE,GYROS,UNKNOWN)"' - id: 'blank_41' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'date_obs' type: str size: 80 doc: '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)"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-OBS' - id: 'time_obs' type: str size: 80 doc: 'TIME-OBS: A keyword the FITS Standard doesn''t define. This record''s comment: "UT time of start of observation (hh:mm:ss)"' - id: 'expstart' type: str size: 80 doc: 'EXPSTART: A keyword the FITS Standard doesn''t define. This record''s comment: "exposure start time (Modified Julian Date)"' - id: 'expend' type: str size: 80 doc: 'EXPEND: A keyword the FITS Standard doesn''t define. This record''s comment: "exposure end time (Modified Julian Date)"' - id: 'exptime' type: str size: 80 doc: 'EXPTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "exposure duration (seconds)--calculated"' - id: 'expflag' type: str size: 80 doc: 'EXPFLAG: A keyword the FITS Standard doesn''t define. This record''s comment: "Exposure interruption indicator"' - id: 'blank_42' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_43' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'targname' type: str size: 80 doc: 'TARGNAME: A keyword the FITS Standard doesn''t define. This record''s comment: "proposer''s target name"' - id: 'ra_targ' type: str size: 80 doc: 'RA_TARG: A keyword the FITS Standard doesn''t define. This record''s comment: "right ascension of the target (deg) (J2000)"' - id: 'dec_targ' type: str size: 80 doc: 'DEC_TARG: A keyword the FITS Standard doesn''t define. This record''s comment: "declination of the target (deg) (J2000)"' - id: 'ecl_long' type: str size: 80 doc: 'ECL_LONG: A keyword the FITS Standard doesn''t define. This record''s comment: "ecliptic longitude of the target (deg) (J2000)"' - id: 'ecl_lat' type: str size: 80 doc: 'ECL_LAT: A keyword the FITS Standard doesn''t define. This record''s comment: "ecliptic latitude of the target (deg) (J2000)"' - id: 'gal_long' type: str size: 80 doc: 'GAL_LONG: A keyword the FITS Standard doesn''t define. This record''s comment: "galactic longitude of the target (deg) (J2000)"' - id: 'gal_lat' type: str size: 80 doc: 'GAL_LAT: A keyword the FITS Standard doesn''t define. This record''s comment: "galactic latitude of the target (deg) (J2000)"' - id: 'blank_44' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'proposid' type: str size: 80 doc: 'PROPOSID: A keyword the FITS Standard doesn''t define. This record''s comment: "PEP proposal identifier"' - id: 'pep_expo' type: str size: 80 doc: 'PEP_EXPO: A keyword the FITS Standard doesn''t define. This record''s comment: "PEP exposure identifier including sequence"' - id: 'linenum' type: str size: 80 doc: 'LINENUM: A keyword the FITS Standard doesn''t define. This record''s comment: "PEP proposal line number"' - id: 'seqline' type: str size: 80 doc: 'SEQLINE: A keyword the FITS Standard doesn''t define. This record''s comment: "PEP line number of defined sequence"' - id: 'seqname' type: str size: 80 doc: 'SEQNAME: A keyword the FITS Standard doesn''t define. This record''s comment: "PEP define/use sequence name"' - id: 'history' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_2' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_3' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_4' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_5' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_6' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_7' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_8' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_9' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_10' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_11' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_12' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_13' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_14' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_15' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_16' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_17' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_18' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_19' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_20' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_21' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_22' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_23' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_24' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_25' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_26' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_27' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_28' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_29' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_30' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_31' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_32' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_33' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_34' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_35' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_36' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_37' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_38' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'skysub1' type: str size: 80 doc: 'SKYSUB1: A keyword the FITS Standard doesn''t define. This record''s comment: "Sky value for chip 1"' - id: 'pys_vers' type: str size: 80 doc: 'PYS_VERS: A keyword the FITS Standard doesn''t define. This record''s comment: "PyStack.py: Version"' - id: 'iraf_i' type: str size: 80 doc: 'IRAF_I: A keyword the FITS Standard doesn''t define.' - id: 'stac_i' type: str size: 80 doc: 'STAC_I: A keyword the FITS Standard doesn''t define.' - id: 'pys_iter' type: str size: 80 doc: 'PYS_ITER: A keyword the FITS Standard doesn''t define. This record''s comment: "PyStack.py: Number of iterations"' - id: 'pys_hexp' type: str size: 80 doc: 'PYS_HEXP: A keyword the FITS Standard doesn''t define. This record''s comment: "PyStack.py: Value of exponent"' - id: 'skysub2' type: str size: 80 doc: 'SKYSUB2: A keyword the FITS Standard doesn''t define. This record''s comment: "Sky value for chip 2"' - id: 'skysub3' type: str size: 80 doc: 'SKYSUB3: A keyword the FITS Standard doesn''t define. This record''s comment: "Sky value for chip 3"' - id: 'skysub4' type: str size: 80 doc: 'SKYSUB4: A keyword the FITS Standard doesn''t define. This record''s comment: "Sky value for chip 4"' - id: 'ncombine' type: str size: 80 doc: 'NCOMBINE: A keyword the FITS Standard doesn''t define. This record''s comment: "Number of exposures for this association"' - id: 'history_39' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'end' type: str size: 80 doc: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/END' - id: 'fill' size: 2400 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu1_image': doc: 'Image row: One row of the 100 x 100 array of HDU 1, the primary HDU, a 100 x 100 array: 100 pixels along axis 1.' seq: - id: 'pixel' type: f4 repeat: expr repeat-expr: 100 doc: 'Pixel value: The values of the 100 x 100 array of HDU 1, the primary HDU, a 100 x 100 array, IEEE single-precision floating point (BITPIX = -32), one row of 100 values per "hdu1_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN.'

Linked from