FITS file FGSf64y0106m_a1f.fits: Kaitai Struct description

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

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 FGSf64y0106m_a1f.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file FGSf64y0106m_a1f.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_fgsf64y0106m_a1f_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): 2 HDUs. hdu1: HDU 1, the primary HDU, a 89688 x 7 array hdu2: HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns 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 89688 x 7 array: The header of HDU 1, the primary HDU, a 89688 x 7 array: 232 keyword records of 80 ASCII characters, the last END, in 7 blocks.' - id: 'hdu1_image' type: 'hdu1_image' repeat: expr repeat-expr: 7 doc: 'Image row: One row of the 89688 x 7 array of HDU 1, the primary HDU, a 89688 x 7 array: 89688 pixels along axis 1.' - id: 'hdu1_fill' size: 96 doc: 'Fill: Fill after the data of HDU 1, the primary HDU, a 89688 x 7 array, to a whole number of 2880-byte blocks.' - id: 'hdu2_header' type: 'hdu2_header' doc: 'Header of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: The header of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: 54 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu2_row' type: 'hdu2_row' repeat: expr repeat-expr: 7 doc: 'Table row: One of the 7 rows of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns, 99 characters (NAXIS1).' - id: 'hdu2_fill' size: 2187 doc: 'Fill: Fill after the data of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, a 89688 x 7 array: The header of HDU 1, the primary HDU, a 89688 x 7 array: 232 keyword records of 80 ASCII characters, the last END, in 7 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: "data 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: "bits per data value"' 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 first data axis"' 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 second data axis"' 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: "File may contain standard extensions"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTEND' - id: 'nextend' type: str size: 80 doc: 'NEXTEND: A keyword the FITS Standard doesn''t define. This record''s comment: "Number of standard extensions"' - id: 'groups' type: str size: 80 doc: 'GROUPS: The value field shall contain the logical constant T. The value T associated with this keyword implies that random-groups records are present. This record''s comment: "image is in group format"' doc-ref: 'http://ontology.oais.info/fits/keyword/GROUPS' - 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 this file was written (yyyy-mm-dd)"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE' - id: 'filename' type: str size: 80 doc: 'FILENAME: A keyword the FITS Standard doesn''t define. This record''s comment: "name of file"' - 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: 'bscale' type: str size: 80 doc: 'BSCALE: This keyword shall be used, along with the BZERO keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. This record''s comment: "scale factor for array value to physical value"' doc-ref: 'http://ontology.oais.info/fits/keyword/BSCALE' - id: 'bzero' type: str size: 80 doc: 'BZERO: This keyword shall be used, along with the BSCALE keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. The value field shall contain a floating-point number representing the physical value corresponding to an array value of zero. The default value for this keyword is 0.0. This record''s comment: "physical value for an array value of zero"' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - 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: 'primesi' type: str size: 80 doc: 'PRIMESI: A keyword the FITS Standard doesn''t define. This record''s comment: "instrument designated as prime"' - 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: '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: '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: 'proposid' type: str size: 80 doc: 'PROPOSID: A keyword the FITS Standard doesn''t define. This record''s comment: "PEP proposal identifier"' - id: 'linenum' type: str size: 80 doc: 'LINENUM: A keyword the FITS Standard doesn''t define. This record''s comment: "proposal logsheet line number"' - id: 'pr_inv_l' type: str size: 80 doc: 'PR_INV_L: A keyword the FITS Standard doesn''t define. This record''s comment: "last name of principal investigator"' - id: 'pr_inv_f' type: str size: 80 doc: 'PR_INV_F: A keyword the FITS Standard doesn''t define. This record''s comment: "first name of principal investigator"' - id: 'pr_inv_m' type: str size: 80 doc: 'PR_INV_M: A keyword the FITS Standard doesn''t define. This record''s comment: "middle name / initial of principal investigat"' - 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: 'orientat' type: str size: 80 doc: 'ORIENTAT: A keyword the FITS Standard doesn''t define. This record''s comment: "position angle of image y axis (deg. e of n)"' - 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_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: '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_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: '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: '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, . . .). This record''s comment: "x-coordinate of reference pixel"' 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, . . .). This record''s comment: "y-coordinate of reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'crval1' type: str size: 80 doc: 'CRVAL1: World-coordinate value at the reference point of Axis i. This record''s comment: "first axis value at reference pixel"' 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. This record''s comment: "second axis value at reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - 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. This record''s comment: "the coordinate type for the first axis"' 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. This record''s comment: "Extra dimension axis name"' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - 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. This record''s comment: "partial of first axis coordinate w.r.t. x"' 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. This record''s comment: "partial of first axis coordinate w.r.t. y"' 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. This record''s comment: "partial of second axis coordinate w.r.t. x"' 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. This record''s comment: "partial of second axis coordinate w.r.t. y"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDi_j' - id: 'datamin' type: str size: 80 doc: '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: "the minimum value of the data"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATAMIN' - id: 'datamax' type: str size: 80 doc: '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: "the maximum value of the data"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATAMAX' - 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: '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: 'opsize' type: str size: 80 doc: 'OPSIZE: A keyword the FITS Standard doesn''t define. This record''s comment: "PSIZE of original image"' - id: 'odattype' type: str size: 80 doc: 'ODATTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "original datatype: 32 bit integer"' - id: 'sdasmgnu' type: str size: 80 doc: 'SDASMGNU: A keyword the FITS Standard doesn''t define. This record''s comment: "number of groups in original image"' - id: 'allg_max' type: str size: 80 doc: 'ALLG-MAX: A keyword the FITS Standard doesn''t define. This record''s comment: "maximum data value in all groups"' - id: 'allg_min' type: str size: 80 doc: 'ALLG-MIN: A keyword the FITS Standard doesn''t define. This record''s comment: "minimum data value in all groups"' - 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: '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: 'gtype1' type: str size: 80 doc: 'GTYPE1: A keyword the FITS Standard doesn''t define. This record''s comment: "PMT A Fine Counts in X direction"' - id: 'gtype2' type: str size: 80 doc: 'GTYPE2: A keyword the FITS Standard doesn''t define. This record''s comment: "PMT B Fine Counts in X direction"' - id: 'gtype3' type: str size: 80 doc: 'GTYPE3: A keyword the FITS Standard doesn''t define. This record''s comment: "PMT A Fine Counts in Y direction"' - id: 'gtype4' type: str size: 80 doc: 'GTYPE4: A keyword the FITS Standard doesn''t define. This record''s comment: "PMT B Fine Counts in Y direction"' - id: 'gtype5' type: str size: 80 doc: 'GTYPE5: A keyword the FITS Standard doesn''t define. This record''s comment: "A Star Selector Position"' - id: 'gtype6' type: str size: 80 doc: 'GTYPE6: A keyword the FITS Standard doesn''t define. This record''s comment: "B Star Selector Position"' - id: 'gtype7' type: str size: 80 doc: 'GTYPE7: A keyword the FITS Standard doesn''t define. This record''s comment: "FGS STATUS FLAGS"' - 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: '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: 'progrmid' type: str size: 80 doc: 'PROGRMID: A keyword the FITS Standard doesn''t define. This record''s comment: "program id (base 36)"' - id: 'obset_id' type: str size: 80 doc: 'OBSET_ID: A keyword the FITS Standard doesn''t define. This record''s comment: "observation set id"' - id: 'observtn' type: str size: 80 doc: 'OBSERVTN: A keyword the FITS Standard doesn''t define. This record''s comment: "observation number (base 36)"' - id: 'schdunit' type: str size: 80 doc: 'SCHDUNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "OMS Scheduling Unit Processing Telemet"' - id: 'ntgts' type: str size: 80 doc: 'NTGTS: A keyword the FITS Standard doesn''t define. This record''s comment: "NUMBER OF TARGETS"' - id: 'fgsno' type: str size: 80 doc: 'FGSNO: A keyword the FITS Standard doesn''t define. This record''s comment: "FGS NUMBER FOR THIS FILE"' - id: 'fgsid' type: str size: 80 doc: 'FGSID: A keyword the FITS Standard doesn''t define. This record''s comment: "ID OF ASTROMETRY FGS"' - id: 'fill1' type: str size: 80 doc: 'FILL1: A keyword the FITS Standard doesn''t define. This record''s comment: "DATA VALUE FOR END-OF-ARRAY FILL"' - id: 'fill2' type: str size: 80 doc: 'FILL2: A keyword the FITS Standard doesn''t define. This record''s comment: "DATA VALUE FOR BAD DATA FILL"' - id: 'tmfmt' type: str size: 80 doc: 'TMFMT: A keyword the FITS Standard doesn''t define. This record''s comment: "TELEMETRY FORMAT (AF, AN, FF, FN, HF, HN)"' - id: 'ftype' type: str size: 80 doc: 'FTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "DATA TYPE (RAW = RAW DATA, SDAS = PROCESSED DAT"' - id: 'pastmode' type: str size: 80 doc: 'PASTMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "PREDICTED ASTROMETRY MODE"' - id: 'aastmode' type: str size: 80 doc: 'AASTMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL ASTROMETRY PROCESSING MODE"' - id: 'datafils' type: str size: 80 doc: 'DATAFILS: A keyword the FITS Standard doesn''t define. This record''s comment: "DOES FILE SET CONTAIN DATA FILES? (T/F)"' - id: 'acqreslt' type: str size: 80 doc: 'ACQRESLT: A keyword the FITS Standard doesn''t define. This record''s comment: "RESULT OF ACQUISITION PROCEDURE"' - id: 'srchtime' type: str size: 80 doc: 'SRCHTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "start time of target search (MJD)"' - id: 'badminfr' type: str size: 80 doc: 'BADMINFR: A keyword the FITS Standard doesn''t define. This record''s comment: "PERCENT BAD MINOR FRAMES"' - id: 'endfound' type: str size: 80 doc: 'ENDFOUND: A keyword the FITS Standard doesn''t define. This record''s comment: "PROPER END OF OBS FOUND IN DATA (T/F)"' - 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: '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: 'calecdr' type: str size: 80 doc: 'CALECDR: A keyword the FITS Standard doesn''t define. This record''s comment: "ENCODER ERROR CORRECTION APPLIED"' - id: 'calsidtr' type: str size: 80 doc: 'CALSIDTR: A keyword the FITS Standard doesn''t define. This record''s comment: "DISTORTION CORRECTION APPLIED"' - id: 'calphoto' type: str size: 80 doc: 'CALPHOTO: A keyword the FITS Standard doesn''t define. This record''s comment: "PHOTOMETRIC CALIBRATION APPLIED"' - id: 'calcolor' type: str size: 80 doc: 'CALCOLOR: A keyword the FITS Standard doesn''t define. This record''s comment: "COLOR EFFECT CORRECTION APPLIED"' - id: 'calwedge' type: str size: 80 doc: 'CALWEDGE: A keyword the FITS Standard doesn''t define. This record''s comment: "FILTER WEDGE CORRECTION APPLIED"' - id: 'caltempr' type: str size: 80 doc: 'CALTEMPR: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE EFFECT CORRECTION APPLIED"' - id: 'caldifab' type: str size: 80 doc: 'CALDIFAB: A keyword the FITS Standard doesn''t define. This record''s comment: "DIFFERENTIAL ABERRATION CORRECTION APPLIED"' - id: 'calcycle' type: str size: 80 doc: 'CALCYCLE: A keyword the FITS Standard doesn''t define. This record''s comment: "CYCLING EFFECTS CORRECTION APPLIED"' - id: 'timed' type: str size: 80 doc: 'TIMED: A keyword the FITS Standard doesn''t define. This record''s comment: "DATA WITH FINE ERROR INTERVAL TIMES COMPUTED"' - id: 'centroid' type: str size: 80 doc: 'CENTROID: A keyword the FITS Standard doesn''t define. This record''s comment: "CENTROIDED FLAG"' - 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: '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: 'puts' type: str size: 80 doc: 'PUTS: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED UT START OF OBS SET (YYYYDDDHHMMSS)"' - id: 'pccs' type: str size: 80 doc: 'PCCS: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED S/C CLOCK CNT, START OBS SET"' - id: 'pute' type: str size: 80 doc: 'PUTE: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED UT END OF OBS SET (YYYYDDDHHMMSS)"' - id: 'pcce' type: str size: 80 doc: 'PCCE: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED S/C CLOCK CNT, END OBS SET"' - id: 'utc0_hi' type: str size: 80 doc: 'UTC0_HI: A keyword the FITS Standard doesn''t define. This record''s comment: "UTC(0) MOST SIGNIFICANT 32 BITS"' - id: 'utc0_lo' type: str size: 80 doc: 'UTC0_LO: A keyword the FITS Standard doesn''t define. This record''s comment: "UTC(0) LEAST SIGNIFICANT 32 BITS"' - id: 't0' type: str size: 80 doc: 'T0: A keyword the FITS Standard doesn''t define. This record''s comment: "T(0)"' - id: 'r0' type: str size: 80 doc: 'R0: A keyword the FITS Standard doesn''t define. This record''s comment: "R(0)"' - id: 'd0' type: str size: 80 doc: 'D0: A keyword the FITS Standard doesn''t define. This record''s comment: "D(0)"' - id: 'putos' type: str size: 80 doc: 'PUTOS: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED UT OBS START (YYYYDDDHHMMSS)"' - id: 'psc_clk' type: str size: 80 doc: 'PSC_CLK: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED S/C CLK CNT AT OBS START"' - id: 'pdur_ob' type: str size: 80 doc: 'PDUR_OB: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED DURATION OF OBS (SEC)"' - id: 'autos' type: str size: 80 doc: 'AUTOS: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL UT OBS START (YYYYDDDHHMMSS)"' - id: 'asc_clk' type: str size: 80 doc: 'ASC_CLK: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL S/C CLK CNT AT OBS START"' - id: 'adur_ob' type: str size: 80 doc: 'ADUR_OB: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL DURATION OF OBS (SEC)"' - id: 'prav1' type: str size: 80 doc: 'PRAV1: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED RA, V1 AXIS, OBSET START (DEG)"' - id: 'pdecv1' type: str size: 80 doc: 'PDECV1: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED DEC, V1 AXIS, OBSET START (DEG)"' - id: 'prolv3' type: str size: 80 doc: 'PROLV3: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED ROLL, V3 AXIS, OBSET START (DEG)"' - id: 'pratgt' type: str size: 80 doc: 'PRATGT: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED RA OF TARGET (DEG)"' - id: 'pdectgt' type: str size: 80 doc: 'PDECTGT: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED DEC OF TARGET (DEG)"' - id: 'fgsrefv2' type: str size: 80 doc: 'FGSREFV2: A keyword the FITS Standard doesn''t define. This record''s comment: "FGS aperture reference V2 position (arcsec)"' - id: 'fgsrefv3' type: str size: 80 doc: 'FGSREFV3: A keyword the FITS Standard doesn''t define. This record''s comment: "FGS aperture reference V3 position (arcsec)"' - id: 'fgs_pav3' type: str size: 80 doc: 'FGS_PAV3: A keyword the FITS Standard doesn''t define. This record''s comment: "FGS aperture position angle of V3-axis (deg)"' - id: 'fgsoffv2' type: str size: 80 doc: 'FGSOFFV2: A keyword the FITS Standard doesn''t define. This record''s comment: "V2 offset from the FGS aper ref position (arcse"' - id: 'fgsoffv3' type: str size: 80 doc: 'FGSOFFV3: A keyword the FITS Standard doesn''t define. This record''s comment: "V3 offset from the FGS aper ref position (arcse"' - id: 'px_pos' type: str size: 80 doc: 'PX_POS: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HST X-COMP POS, OBS START (KM)"' - id: 'py_pos' type: str size: 80 doc: 'PY_POS: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HST Y-COMP POS, OBS START (KM)"' - id: 'pz_pos' type: str size: 80 doc: 'PZ_POS: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HST Z-COMP POS, OBS START (KM)"' - id: 'px_vel' type: str size: 80 doc: 'PX_VEL: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HST X-COMP VEL WRT EARTH (KM/SEC)"' - id: 'py_vel' type: str size: 80 doc: 'PY_VEL: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HST Y-COMP VEL WRT EARTH (KM/SEC)"' - id: 'pz_vel' type: str size: 80 doc: 'PZ_VEL: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HST Z-COMP VEL WRT EARTH (KM/SEC)"' - id: 'pvel_ab' type: str size: 80 doc: 'PVEL_AB: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED VEL ABERRATION (ARCSEC)"' - id: 'ph_prlx' type: str size: 80 doc: 'PH_PRLX: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED HORIZ PARALLAX (ARCSEC)"' - id: 'pa_prlx' type: str size: 80 doc: 'PA_PRLX: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED ANNUAL PARALLAX (ARCSEC)"' - id: 'dist' type: str size: 80 doc: 'DIST: A keyword the FITS Standard doesn''t define. This record''s comment: "DISTANCE TO TARGET (KM)"' - id: 'perssa' type: str size: 80 doc: 'PERSSA: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED SSA ENCODER READING OF THIS FGS"' - id: 'perssb' type: str size: 80 doc: 'PERSSB: A keyword the FITS Standard doesn''t define. This record''s comment: "PRED SSB ENCODER READING OF THIS FGS"' - id: 'cavg_tim' type: str size: 80 doc: 'CAVG_TIM: A keyword the FITS Standard doesn''t define. This record''s comment: "COMMANDED AVG TIME IN AST FGS (SEC)"' - id: 'aavg_tim' type: str size: 80 doc: 'AAVG_TIM: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL AVG TIME IN AST FGS (SEC)"' - id: 'tgt_mag' type: str size: 80 doc: 'TGT_MAG: A keyword the FITS Standard doesn''t define. This record''s comment: "TARGET MAGNITUDE"' - id: 'cast_flt' type: str size: 80 doc: 'CAST_FLT: A keyword the FITS Standard doesn''t define. This record''s comment: "COMMANDED AST FGS FILTER POS"' - id: 'aast_flt' type: str size: 80 doc: 'AAST_FLT: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL AST FGS FILTER POS"' - id: 'targetid' type: str size: 80 doc: 'TARGETID: A keyword the FITS Standard doesn''t define. This record''s comment: "TARGET IDENTIFICATION"' - id: 'pstarid' type: str size: 80 doc: 'PSTARID: A keyword the FITS Standard doesn''t define. This record''s comment: "PREDICTED STAR IDENTIFIER (-1 - 255)"' - id: 'astarid' type: str size: 80 doc: 'ASTARID: A keyword the FITS Standard doesn''t define. This record''s comment: "ACTUAL STAR IDENTIFIER (-1 - 255)"' - id: 'astarno' type: str size: 80 doc: 'ASTARNO: A keyword the FITS Standard doesn''t define. This record''s comment: "POSITION OF ACTUAL GUIDE STAR ON LIST (-1 - 20)"' - 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: '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: 'k1x' type: str size: 80 doc: 'K1X: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'k3x' type: str size: 80 doc: 'K3X: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k1y' type: str size: 80 doc: 'K1Y: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'k3y' type: str size: 80 doc: 'K3Y: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k6' type: str size: 80 doc: 'K6: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k7' type: str size: 80 doc: 'K7: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k8' type: str size: 80 doc: 'K8: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'ka' type: str size: 80 doc: 'KA: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'kg' type: str size: 80 doc: 'KG: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'kj' type: str size: 80 doc: 'KJ: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'ky' type: str size: 80 doc: 'KY: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN**2/SEC)"' - id: 'k10' type: str size: 80 doc: 'K10: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k13' type: str size: 80 doc: 'K13: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k14' type: str size: 80 doc: 'K14: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k15' type: str size: 80 doc: 'K15: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k16' type: str size: 80 doc: 'K16: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCSEC/SEC)"' - id: 'kb' type: str size: 80 doc: 'KB: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'kd' type: str size: 80 doc: 'KD: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'kz' type: str size: 80 doc: 'KZ: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'k5' type: str size: 80 doc: 'K5: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'km' type: str size: 80 doc: 'KM: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'kn' type: str size: 80 doc: 'KN: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'ke' type: str size: 80 doc: 'KE: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'kf' type: str size: 80 doc: 'KF: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCSEC)"' - id: 'k30' type: str size: 80 doc: 'K30: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k31' type: str size: 80 doc: 'K31: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCSEC/SEC)"' - id: 'k0x' type: str size: 80 doc: 'K0X: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'k11' type: str size: 80 doc: 'K11: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k0y' type: str size: 80 doc: 'K0Y: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'k18' type: str size: 80 doc: 'K18: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCMIN)"' - id: 'k9' type: str size: 80 doc: 'K9: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k20' type: str size: 80 doc: 'K20: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCSEC)"' - id: 'k21' type: str size: 80 doc: 'K21: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (ARCSEC)"' - id: 'k22' type: str size: 80 doc: 'K22: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k23' type: str size: 80 doc: 'K23: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k24' type: str size: 80 doc: 'K24: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'k25' type: str size: 80 doc: 'K25: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS"' - id: 'kh' type: str size: 80 doc: 'KH: A keyword the FITS Standard doesn''t define. This record''s comment: "K-FACTOR FOR THIS FGS (DEG)"' - 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: '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: 'temp21' type: str size: 80 doc: 'TEMP21: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE SENSOR 2 COUNTS FOR FGS 1"' - id: 'temp31' type: str size: 80 doc: 'TEMP31: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE SENSOR 3 COUNTS FOR FGS 1"' - id: 'temp41' type: str size: 80 doc: 'TEMP41: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE SENSOR 4 COUNTS FOR FGS 1"' - id: 'temp61' type: str size: 80 doc: 'TEMP61: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE SENSOR 6 COUNTS FOR FGS 1"' - id: 'temp71' type: str size: 80 doc: 'TEMP71: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE SENSOR 7 COUNTS FOR FGS 1"' - id: 'temp91' type: str size: 80 doc: 'TEMP91: A keyword the FITS Standard doesn''t define. This record''s comment: "TEMPERATURE SENSOR 9 COUNTS FOR FGS 1"' - 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: '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: 'avgxapmt' type: str size: 80 doc: 'AVGXAPMT: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG X,A PMT COUNTS (PER FE TIME)"' - id: 'avgxbpmt' type: str size: 80 doc: 'AVGXBPMT: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG X,B PMT COUNTS (PER FE TIME)"' - id: 'avgyapmt' type: str size: 80 doc: 'AVGYAPMT: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG Y,A PMT COUNTS (PER FE TIME)"' - id: 'avgybpmt' type: str size: 80 doc: 'AVGYBPMT: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG Y,B PMT COUNTS (PER FE TIME)"' - id: 'avgfesx' type: str size: 80 doc: 'AVGFESX: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG FES IN X (ARCSEC)"' - id: 'avgfesy' type: str size: 80 doc: 'AVGFESY: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG FES IN Y (ARCSEC)"' - id: 'avga_bx' type: str size: 80 doc: 'AVGA_BX: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG <A+B> IN X (COUNTS)"' - id: 'avga_by' type: str size: 80 doc: 'AVGA_BY: A keyword the FITS Standard doesn''t define. This record''s comment: "AVG <A+B> IN Y (COUNTS)"' - id: 'avgint' type: str size: 80 doc: 'AVGINT: A keyword the FITS Standard doesn''t define. This record''s comment: "ACT AVG TIME COVERED BY FINE ERR AVG TIME INT ("' - 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: '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: 1600 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 89688 x 7 array of HDU 1, the primary HDU, a 89688 x 7 array: 89688 pixels along axis 1.' seq: - id: 'pixel' type: s4 repeat: expr repeat-expr: 89688 doc: 'Pixel value: The values of the 89688 x 7 array of HDU 1, the primary HDU, a 89688 x 7 array, 32-bit two''s complement integers (BITPIX = 32), one row of 89688 values per "hdu1_image" record. Axis 1: SECONDS. Axis 2: GROUP_NUMBER. Physical value = BZERO + BSCALE x stored value. Physical value = raw * 1.0 + 0.0.' 'hdu2_header': doc: 'Header of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: The header of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: 54 keyword records of 80 ASCII characters, the last END, in 2 blocks.' seq: - id: 'xtension' type: str size: 80 doc: '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: "extension type"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - 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: "bits per data value"' 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 first data axis"' 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 second data axis"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: '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: "number of group parameters"' doc-ref: 'http://ontology.oais.info/fits/keyword/PCOUNT' - id: 'gcount' type: str size: 80 doc: '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: "number of groups"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'tfields' type: str size: 80 doc: 'TFIELDS: The value field shall contain a non-negative integer representing the number of fields in each row. The maximum permissible value is 999. This record''s comment: "number of fields in each table row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - id: 'inherit' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'extname' type: str size: 80 doc: '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"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'extver' type: str size: 80 doc: '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 number"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTVER' - 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: 'expname' type: str size: 80 doc: 'EXPNAME: A keyword the FITS Standard doesn''t define. This record''s comment: "9 character exposure identifier"' - 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: '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: 'ttype1' type: str size: 80 doc: 'TTYPE1: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "minimum value of the data for FGS group"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol1' type: str size: 80 doc: 'TBCOL1: The TBCOLn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain an integer specifying the column in which Field n starts. The first column of a row is numbered 1. This record''s comment: "column in which field 1 starts"' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform1' type: str size: 80 doc: 'TFORM1: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN-77 format in which field 1 is coded"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit1' type: str size: 80 doc: 'TUNIT1: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of quantity in field 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp1' type: str size: 80 doc: 'TDISP1: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "FORTRAN-90 format for display of field 1 conten"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype2' type: str size: 80 doc: 'TTYPE2: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "maximum value of the data for FGS group"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol2' type: str size: 80 doc: 'TBCOL2: The TBCOLn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain an integer specifying the column in which Field n starts. The first column of a row is numbered 1. This record''s comment: "column in which field 2 starts"' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform2' type: str size: 80 doc: 'TFORM2: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN-77 format in which field 2 is coded"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit2' type: str size: 80 doc: 'TUNIT2: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of quantity in field 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp2' type: str size: 80 doc: 'TDISP2: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "FORTRAN-90 format for display of field 2 conten"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype3' type: str size: 80 doc: 'TTYPE3: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "reference pixel number"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol3' type: str size: 80 doc: 'TBCOL3: The TBCOLn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain an integer specifying the column in which Field n starts. The first column of a row is numbered 1. This record''s comment: "column in which field 3 starts"' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform3' type: str size: 80 doc: 'TFORM3: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN-77 format in which field 3 is coded"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit3' type: str size: 80 doc: 'TUNIT3: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of quantity in field 3"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp3' type: str size: 80 doc: 'TDISP3: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "FORTRAN-90 format for display of field 3 conten"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype4' type: str size: 80 doc: 'TTYPE4: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "delta time between data points"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol4' type: str size: 80 doc: 'TBCOL4: The TBCOLn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain an integer specifying the column in which Field n starts. The first column of a row is numbered 1. This record''s comment: "column in which field 4 starts"' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform4' type: str size: 80 doc: 'TFORM4: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN-77 format in which field 4 is coded"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit4' type: str size: 80 doc: 'TUNIT4: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of quantity in field 4"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp4' type: str size: 80 doc: 'TDISP4: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "FORTRAN-90 format for display of field 4 conten"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype5' type: str size: 80 doc: 'TTYPE5: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "time of S/C clock for reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol5' type: str size: 80 doc: 'TBCOL5: The TBCOLn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain an integer specifying the column in which Field n starts. The first column of a row is numbered 1. This record''s comment: "column in which field 5 starts"' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform5' type: str size: 80 doc: 'TFORM5: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN-77 format in which field 5 is coded"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit5' type: str size: 80 doc: 'TUNIT5: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of quantity in field 5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp5' type: str size: 80 doc: 'TDISP5: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "FORTRAN-90 format for display of field 5 conten"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype6' type: str size: 80 doc: 'TTYPE6: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "coordinate type for the first axis"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol6' type: str size: 80 doc: 'TBCOL6: The TBCOLn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain an integer specifying the column in which Field n starts. The first column of a row is numbered 1. This record''s comment: "column in which field 6 starts"' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform6' type: str size: 80 doc: 'TFORM6: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN-77 format in which field 6 is coded"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit6' type: str size: 80 doc: 'TUNIT6: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of quantity in field 6"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp6' type: str size: 80 doc: 'TDISP6: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "FORTRAN-90 format for display of field 6 conten"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: '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: 1440 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu2_row': doc: 'Table row: One of the 7 rows of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns, 99 characters (NAXIS1).' seq: - id: 'datamin' type: str size: 15 doc: 'DATAMIN: Column 1 of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: TFORM1 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 1 (TBCOL1). Minimum value of the data for FGS group.' - id: 'gap_2' type: str size: 1 doc: 'Gap: Characters before column 2 that no column uses.' - id: 'datamax' type: str size: 15 doc: 'DATAMAX: Column 2 of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: TFORM2 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 17 (TBCOL2). Maximum value of the data for FGS group.' - id: 'gap_3' type: str size: 1 doc: 'Gap: Characters before column 3 that no column uses.' - id: 'crpix1' type: str size: 15 doc: 'CRPIX1: Column 3 of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: TFORM3 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 33 (TBCOL3). Reference pixel number.' - id: 'gap_4' type: str size: 1 doc: 'Gap: Characters before column 4 that no column uses.' - id: 'cd1_1' type: str size: 15 doc: 'CD1_1: Column 4 of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: TFORM4 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 49 (TBCOL4). Delta time between data points.' - id: 'gap_5' type: str size: 1 doc: 'Gap: Characters before column 5 that no column uses.' - id: 'crval1' type: str size: 25 doc: 'CRVAL1: Column 5 of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: TFORM5 = ''D25.17'', a decimal number with an exponent written in 25 characters from character 65 (TBCOL5). Time of S/C clock for reference pixel.' - id: 'gap_6' type: str size: 1 doc: 'Gap: Characters before column 6 that no column uses.' - id: 'ctype1' type: str size: 8 doc: 'CTYPE1: Column 6 of HDU 2, an ASCII table (EXTNAME ''f64y0106m_cvt.a1h.tab'') of 7 rows of 6 columns: TFORM6 = ''A8'', characters written in 8 characters from character 91 (TBCOL6). Coordinate type for the first axis.' - id: 'spare' type: str size: 1 doc: 'Spare: Characters at the end of each row that no column uses.'

Linked from