FITS file WFPC2u5780205r_c0fx.fits: Kaitai Struct description

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

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 WFPC2u5780205r_c0fx.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file WFPC2u5780205r_c0fx.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_wfpc2u5780205r_c0fx_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 200 x 200 x 4 array hdu2: HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 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 200 x 200 x 4 array: The header of HDU 1, the primary HDU, a 200 x 200 x 4 array: 263 keyword records of 80 ASCII characters, the last END, in 8 blocks.' - id: 'hdu1_image' type: 'hdu1_image' repeat: expr repeat-expr: 800 doc: 'Image row: One row of the 200 x 200 x 4 array of HDU 1, the primary HDU, a 200 x 200 x 4 array: 200 pixels along axis 1; the rows of each plane follow one another.' - id: 'hdu1_fill' size: 2240 doc: 'Fill: Fill after the data of HDU 1, the primary HDU, a 200 x 200 x 4 array, to a whole number of 2880-byte blocks.' - id: 'hdu2_header' type: 'hdu2_header' doc: 'Header of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: The header of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: 354 keyword records of 80 ASCII characters, the last END, in 10 blocks.' - id: 'hdu2_row' type: 'hdu2_row' repeat: expr repeat-expr: 4 doc: 'Table row: One of the 4 rows of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns, 796 characters (NAXIS1).' - id: 'hdu2_fill' size: 2576 doc: 'Fill: Fill after the data of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, a 200 x 200 x 4 array: The header of HDU 1, the primary HDU, a 200 x 200 x 4 array: 263 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: 'naxis3' type: str size: 80 doc: 'NAXIS3: 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 3"' 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: '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: "REAL = TAPE*BSCALE + BZERO"' 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - 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: '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: "Fitsio version 21-Feb-1996"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'fitsdate' type: str size: 80 doc: 'FITSDATE: A keyword the FITS Standard doesn''t define. This record''s comment: "Date FITS file was created"' - id: 'filename' type: str size: 80 doc: 'FILENAME: A keyword the FITS Standard doesn''t define. This record''s comment: "Original filename"' - id: 'allg_max' type: str size: 80 doc: 'ALLG-MAX: A keyword the FITS Standard doesn''t define. This record''s comment: "Data max 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: "Data min in all groups"' - id: 'odattype' type: str size: 80 doc: 'ODATTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Original datatype: Single precision real"' - 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: '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: '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: "DATA MIN"' 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: "DATA MAX"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATAMAX' - 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: 'origin_2' 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.' 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.' - 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: 'ctype3' type: str size: 80 doc: 'CTYPE3: 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: 'cd3_3' type: str size: 80 doc: 'CD3_3: 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: 'cd3_1' type: str size: 80 doc: 'CD3_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_3' type: str size: 80 doc: 'CD1_3: 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_3' type: str size: 80 doc: 'CD2_3: 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: 'cd3_2' type: str size: 80 doc: 'CD3_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: '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: 2000 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 200 x 200 x 4 array of HDU 1, the primary HDU, a 200 x 200 x 4 array: 200 pixels along axis 1; the rows of each plane follow one another.' seq: - id: 'pixel' type: f4 repeat: expr repeat-expr: 200 doc: 'Pixel value: The values of the 200 x 200 x 4 array of HDU 1, the primary HDU, a 200 x 200 x 4 array, IEEE single-precision floating point (BITPIX = -32), one row of 200 values per "hdu1_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN. Axis 3: 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 ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: The header of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: 354 keyword records of 80 ASCII characters, the last END, in 10 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: "Ascii table extension"' 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: "8-bits per ''pixels''"' 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: "Simple 2-D matrix"' 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: "Number of characters per row"' 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: "The number of rows"' 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: "No ''random'' 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: "Only one group"' 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 per row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - 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: "Name of table"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - 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: '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.' 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.' 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.' 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.' 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: "%25.16g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: '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.' 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.' 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.' 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.' 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: "%25.16g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: '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.' 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.' 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.' 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.' 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: "%15.7g"' 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: '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.' 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.' 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.' 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.' 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: "%15.7g"' 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: '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.' 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.' 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.' 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.' 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: "%15.7g"' 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: '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.' 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.' 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.' 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.' 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: "%15.7g"' 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: 'ttype7' type: str size: 80 doc: 'TTYPE7: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol7' type: str size: 80 doc: 'TBCOL7: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform7' type: str size: 80 doc: 'TFORM7: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit7' type: str size: 80 doc: 'TUNIT7: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp7' type: str size: 80 doc: 'TDISP7: 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: "%15.7g"' 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: 'ttype8' type: str size: 80 doc: 'TTYPE8: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol8' type: str size: 80 doc: 'TBCOL8: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform8' type: str size: 80 doc: 'TFORM8: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit8' type: str size: 80 doc: 'TUNIT8: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp8' type: str size: 80 doc: 'TDISP8: 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: "%15.7g"' 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: 'ttype9' type: str size: 80 doc: 'TTYPE9: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol9' type: str size: 80 doc: 'TBCOL9: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform9' type: str size: 80 doc: 'TFORM9: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit9' type: str size: 80 doc: 'TUNIT9: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp9' type: str size: 80 doc: 'TDISP9: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype10' type: str size: 80 doc: 'TTYPE10: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol10' type: str size: 80 doc: 'TBCOL10: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform10' type: str size: 80 doc: 'TFORM10: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit10' type: str size: 80 doc: 'TUNIT10: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp10' type: str size: 80 doc: 'TDISP10: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype11' type: str size: 80 doc: 'TTYPE11: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol11' type: str size: 80 doc: 'TBCOL11: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform11' type: str size: 80 doc: 'TFORM11: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit11' type: str size: 80 doc: 'TUNIT11: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp11' type: str size: 80 doc: 'TDISP11: 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: "%1b"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype12' type: str size: 80 doc: 'TTYPE12: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol12' type: str size: 80 doc: 'TBCOL12: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform12' type: str size: 80 doc: 'TFORM12: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit12' type: str size: 80 doc: 'TUNIT12: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp12' type: str size: 80 doc: 'TDISP12: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype13' type: str size: 80 doc: 'TTYPE13: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol13' type: str size: 80 doc: 'TBCOL13: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform13' type: str size: 80 doc: 'TFORM13: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit13' type: str size: 80 doc: 'TUNIT13: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp13' type: str size: 80 doc: 'TDISP13: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype14' type: str size: 80 doc: 'TTYPE14: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol14' type: str size: 80 doc: 'TBCOL14: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform14' type: str size: 80 doc: 'TFORM14: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit14' type: str size: 80 doc: 'TUNIT14: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp14' type: str size: 80 doc: 'TDISP14: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype15' type: str size: 80 doc: 'TTYPE15: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol15' type: str size: 80 doc: 'TBCOL15: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform15' type: str size: 80 doc: 'TFORM15: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit15' type: str size: 80 doc: 'TUNIT15: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp15' type: str size: 80 doc: 'TDISP15: 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: "%25.16g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype16' type: str size: 80 doc: 'TTYPE16: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol16' type: str size: 80 doc: 'TBCOL16: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform16' type: str size: 80 doc: 'TFORM16: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit16' type: str size: 80 doc: 'TUNIT16: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp16' type: str size: 80 doc: 'TDISP16: 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: "%25.16g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype17' type: str size: 80 doc: 'TTYPE17: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol17' type: str size: 80 doc: 'TBCOL17: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform17' type: str size: 80 doc: 'TFORM17: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit17' type: str size: 80 doc: 'TUNIT17: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp17' type: str size: 80 doc: 'TDISP17: 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: "%-8s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype18' type: str size: 80 doc: 'TTYPE18: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol18' type: str size: 80 doc: 'TBCOL18: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform18' type: str size: 80 doc: 'TFORM18: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit18' type: str size: 80 doc: 'TUNIT18: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp18' type: str size: 80 doc: 'TDISP18: 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: "%-8s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype19' type: str size: 80 doc: 'TTYPE19: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol19' type: str size: 80 doc: 'TBCOL19: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform19' type: str size: 80 doc: 'TFORM19: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit19' type: str size: 80 doc: 'TUNIT19: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp19' type: str size: 80 doc: 'TDISP19: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype20' type: str size: 80 doc: 'TTYPE20: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol20' type: str size: 80 doc: 'TBCOL20: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform20' type: str size: 80 doc: 'TFORM20: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit20' type: str size: 80 doc: 'TUNIT20: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp20' type: str size: 80 doc: 'TDISP20: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype21' type: str size: 80 doc: 'TTYPE21: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol21' type: str size: 80 doc: 'TBCOL21: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform21' type: str size: 80 doc: 'TFORM21: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit21' type: str size: 80 doc: 'TUNIT21: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp21' type: str size: 80 doc: 'TDISP21: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype22' type: str size: 80 doc: 'TTYPE22: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol22' type: str size: 80 doc: 'TBCOL22: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform22' type: str size: 80 doc: 'TFORM22: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit22' type: str size: 80 doc: 'TUNIT22: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp22' type: str size: 80 doc: 'TDISP22: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype23' type: str size: 80 doc: 'TTYPE23: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol23' type: str size: 80 doc: 'TBCOL23: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform23' type: str size: 80 doc: 'TFORM23: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit23' type: str size: 80 doc: 'TUNIT23: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp23' type: str size: 80 doc: 'TDISP23: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype24' type: str size: 80 doc: 'TTYPE24: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol24' type: str size: 80 doc: 'TBCOL24: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform24' type: str size: 80 doc: 'TFORM24: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit24' type: str size: 80 doc: 'TUNIT24: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp24' type: str size: 80 doc: 'TDISP24: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype25' type: str size: 80 doc: 'TTYPE25: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol25' type: str size: 80 doc: 'TBCOL25: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform25' type: str size: 80 doc: 'TFORM25: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit25' type: str size: 80 doc: 'TUNIT25: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp25' type: str size: 80 doc: 'TDISP25: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype26' type: str size: 80 doc: 'TTYPE26: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol26' type: str size: 80 doc: 'TBCOL26: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform26' type: str size: 80 doc: 'TFORM26: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit26' type: str size: 80 doc: 'TUNIT26: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp26' type: str size: 80 doc: 'TDISP26: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype27' type: str size: 80 doc: 'TTYPE27: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol27' type: str size: 80 doc: 'TBCOL27: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform27' type: str size: 80 doc: 'TFORM27: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit27' type: str size: 80 doc: 'TUNIT27: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp27' type: str size: 80 doc: 'TDISP27: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype28' type: str size: 80 doc: 'TTYPE28: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol28' type: str size: 80 doc: 'TBCOL28: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform28' type: str size: 80 doc: 'TFORM28: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit28' type: str size: 80 doc: 'TUNIT28: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp28' type: str size: 80 doc: 'TDISP28: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype29' type: str size: 80 doc: 'TTYPE29: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol29' type: str size: 80 doc: 'TBCOL29: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform29' type: str size: 80 doc: 'TFORM29: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit29' type: str size: 80 doc: 'TUNIT29: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp29' type: str size: 80 doc: 'TDISP29: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype30' type: str size: 80 doc: 'TTYPE30: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol30' type: str size: 80 doc: 'TBCOL30: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform30' type: str size: 80 doc: 'TFORM30: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit30' type: str size: 80 doc: 'TUNIT30: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp30' type: str size: 80 doc: 'TDISP30: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype31' type: str size: 80 doc: 'TTYPE31: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol31' type: str size: 80 doc: 'TBCOL31: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform31' type: str size: 80 doc: 'TFORM31: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit31' type: str size: 80 doc: 'TUNIT31: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp31' type: str size: 80 doc: 'TDISP31: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype32' type: str size: 80 doc: 'TTYPE32: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol32' type: str size: 80 doc: 'TBCOL32: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform32' type: str size: 80 doc: 'TFORM32: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit32' type: str size: 80 doc: 'TUNIT32: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp32' type: str size: 80 doc: 'TDISP32: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype33' type: str size: 80 doc: 'TTYPE33: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol33' type: str size: 80 doc: 'TBCOL33: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform33' type: str size: 80 doc: 'TFORM33: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit33' type: str size: 80 doc: 'TUNIT33: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp33' type: str size: 80 doc: 'TDISP33: 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: "%11d"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype34' type: str size: 80 doc: 'TTYPE34: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol34' type: str size: 80 doc: 'TBCOL34: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform34' type: str size: 80 doc: 'TFORM34: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit34' type: str size: 80 doc: 'TUNIT34: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp34' type: str size: 80 doc: 'TDISP34: 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: "%-48s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype35' type: str size: 80 doc: 'TTYPE35: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol35' type: str size: 80 doc: 'TBCOL35: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform35' type: str size: 80 doc: 'TFORM35: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit35' type: str size: 80 doc: 'TUNIT35: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp35' type: str size: 80 doc: 'TDISP35: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype36' type: str size: 80 doc: 'TTYPE36: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol36' type: str size: 80 doc: 'TBCOL36: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform36' type: str size: 80 doc: 'TFORM36: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit36' type: str size: 80 doc: 'TUNIT36: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp36' type: str size: 80 doc: 'TDISP36: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype37' type: str size: 80 doc: 'TTYPE37: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol37' type: str size: 80 doc: 'TBCOL37: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform37' type: str size: 80 doc: 'TFORM37: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit37' type: str size: 80 doc: 'TUNIT37: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp37' type: str size: 80 doc: 'TDISP37: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype38' type: str size: 80 doc: 'TTYPE38: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol38' type: str size: 80 doc: 'TBCOL38: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform38' type: str size: 80 doc: 'TFORM38: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit38' type: str size: 80 doc: 'TUNIT38: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp38' type: str size: 80 doc: 'TDISP38: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype39' type: str size: 80 doc: 'TTYPE39: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol39' type: str size: 80 doc: 'TBCOL39: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform39' type: str size: 80 doc: 'TFORM39: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit39' type: str size: 80 doc: 'TUNIT39: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp39' type: str size: 80 doc: 'TDISP39: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype40' type: str size: 80 doc: 'TTYPE40: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol40' type: str size: 80 doc: 'TBCOL40: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform40' type: str size: 80 doc: 'TFORM40: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit40' type: str size: 80 doc: 'TUNIT40: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp40' type: str size: 80 doc: 'TDISP40: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype41' type: str size: 80 doc: 'TTYPE41: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol41' type: str size: 80 doc: 'TBCOL41: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform41' type: str size: 80 doc: 'TFORM41: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit41' type: str size: 80 doc: 'TUNIT41: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp41' type: str size: 80 doc: 'TDISP41: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype42' type: str size: 80 doc: 'TTYPE42: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol42' type: str size: 80 doc: 'TBCOL42: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform42' type: str size: 80 doc: 'TFORM42: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit42' type: str size: 80 doc: 'TUNIT42: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp42' type: str size: 80 doc: 'TDISP42: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype43' type: str size: 80 doc: 'TTYPE43: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol43' type: str size: 80 doc: 'TBCOL43: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform43' type: str size: 80 doc: 'TFORM43: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit43' type: str size: 80 doc: 'TUNIT43: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp43' type: str size: 80 doc: 'TDISP43: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - 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: 'ttype44' type: str size: 80 doc: 'TTYPE44: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol44' type: str size: 80 doc: 'TBCOL44: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform44' type: str size: 80 doc: 'TFORM44: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit44' type: str size: 80 doc: 'TUNIT44: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp44' type: str size: 80 doc: 'TDISP44: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_45' 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: 'ttype45' type: str size: 80 doc: 'TTYPE45: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol45' type: str size: 80 doc: 'TBCOL45: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform45' type: str size: 80 doc: 'TFORM45: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit45' type: str size: 80 doc: 'TUNIT45: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp45' type: str size: 80 doc: 'TDISP45: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_46' 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: 'ttype46' type: str size: 80 doc: 'TTYPE46: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol46' type: str size: 80 doc: 'TBCOL46: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform46' type: str size: 80 doc: 'TFORM46: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit46' type: str size: 80 doc: 'TUNIT46: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp46' type: str size: 80 doc: 'TDISP46: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_47' 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: 'ttype47' type: str size: 80 doc: 'TTYPE47: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol47' type: str size: 80 doc: 'TBCOL47: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform47' type: str size: 80 doc: 'TFORM47: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit47' type: str size: 80 doc: 'TUNIT47: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp47' type: str size: 80 doc: 'TDISP47: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_48' 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: 'ttype48' type: str size: 80 doc: 'TTYPE48: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol48' type: str size: 80 doc: 'TBCOL48: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform48' type: str size: 80 doc: 'TFORM48: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit48' type: str size: 80 doc: 'TUNIT48: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp48' type: str size: 80 doc: 'TDISP48: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_49' 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: 'ttype49' type: str size: 80 doc: 'TTYPE49: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tbcol49' type: str size: 80 doc: 'TBCOL49: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TBCOLn' - id: 'tform49' type: str size: 80 doc: 'TFORM49: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit49' type: str size: 80 doc: 'TUNIT49: 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp49' type: str size: 80 doc: 'TDISP49: 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: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_50' 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: '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: '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.' 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/DATAMAX' - 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: '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: 480 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 4 rows of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns, 796 characters (NAXIS1).' seq: - id: 'crval1' type: str size: 25 doc: 'CRVAL1: Column 1 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM1 = ''D25.17'', a decimal number with an exponent written in 25 characters from character 1 (TBCOL1).' - id: 'gap_2' type: str size: 1 doc: 'Gap: Characters before column 2 that no column uses.' - id: 'crval2' type: str size: 25 doc: 'CRVAL2: Column 2 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM2 = ''D25.17'', a decimal number with an exponent written in 25 characters from character 27 (TBCOL2).' - 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 ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM3 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 53 (TBCOL3).' - id: 'gap_4' type: str size: 1 doc: 'Gap: Characters before column 4 that no column uses.' - id: 'crpix2' type: str size: 15 doc: 'CRPIX2: Column 4 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM4 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 69 (TBCOL4).' - id: 'gap_5' type: str size: 1 doc: 'Gap: Characters before column 5 that no column uses.' - id: 'cd1_1' type: str size: 15 doc: 'CD1_1: Column 5 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM5 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 85 (TBCOL5).' - id: 'gap_6' type: str size: 1 doc: 'Gap: Characters before column 6 that no column uses.' - id: 'cd1_2' type: str size: 15 doc: 'CD1_2: Column 6 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM6 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 101 (TBCOL6).' - id: 'gap_7' type: str size: 1 doc: 'Gap: Characters before column 7 that no column uses.' - id: 'cd2_1' type: str size: 15 doc: 'CD2_1: Column 7 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM7 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 117 (TBCOL7).' - id: 'gap_8' type: str size: 1 doc: 'Gap: Characters before column 8 that no column uses.' - id: 'cd2_2' type: str size: 15 doc: 'CD2_2: Column 8 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM8 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 133 (TBCOL8).' - id: 'gap_9' type: str size: 1 doc: 'Gap: Characters before column 9 that no column uses.' - id: 'datamin' type: str size: 15 doc: 'DATAMIN: Column 9 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM9 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 149 (TBCOL9).' - id: 'gap_10' type: str size: 1 doc: 'Gap: Characters before column 10 that no column uses.' - id: 'datamax' type: str size: 15 doc: 'DATAMAX: Column 10 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM10 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 165 (TBCOL10).' - id: 'gap_11' type: str size: 1 doc: 'Gap: Characters before column 11 that no column uses.' - id: 'mir_revr' type: str size: 1 doc: 'MIR_REVR (LOGICAL-): Column 11 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM11 = ''A1'', characters written in 1 characters from character 181 (TBCOL11).' - id: 'gap_12' type: str size: 1 doc: 'Gap: Characters before column 12 that no column uses.' - id: 'orientat' type: str size: 15 doc: 'ORIENTAT: Column 12 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM12 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 183 (TBCOL12).' - id: 'gap_13' type: str size: 1 doc: 'Gap: Characters before column 13 that no column uses.' - id: 'fillcnt' type: str size: 12 doc: 'FILLCNT: Column 13 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM13 = ''I12'', a decimal integer written in 12 characters from character 199 (TBCOL13).' - id: 'gap_14' type: str size: 1 doc: 'Gap: Characters before column 14 that no column uses.' - id: 'errcnt' type: str size: 12 doc: 'ERRCNT: Column 14 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM14 = ''I12'', a decimal integer written in 12 characters from character 212 (TBCOL14).' - id: 'gap_15' type: str size: 1 doc: 'Gap: Characters before column 15 that no column uses.' - id: 'fpkttime' type: str size: 25 doc: 'FPKTTIME: Column 15 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM15 = ''D25.17'', a decimal number with an exponent written in 25 characters from character 225 (TBCOL15).' - id: 'gap_16' type: str size: 1 doc: 'Gap: Characters before column 16 that no column uses.' - id: 'lpkttime' type: str size: 25 doc: 'LPKTTIME: Column 16 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM16 = ''D25.17'', a decimal number with an exponent written in 25 characters from character 251 (TBCOL16).' - id: 'gap_17' type: str size: 1 doc: 'Gap: Characters before column 17 that no column uses.' - id: 'ctype1' type: str size: 8 doc: 'CTYPE1 (CHARACTER*8): Column 17 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM17 = ''A8'', characters written in 8 characters from character 277 (TBCOL17).' - id: 'gap_18' type: str size: 1 doc: 'Gap: Characters before column 18 that no column uses.' - id: 'ctype2' type: str size: 8 doc: 'CTYPE2 (CHARACTER*8): Column 18 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM18 = ''A8'', characters written in 8 characters from character 286 (TBCOL18).' - id: 'gap_19' type: str size: 1 doc: 'Gap: Characters before column 19 that no column uses.' - id: 'detector' type: str size: 12 doc: 'DETECTOR: Column 19 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM19 = ''I12'', a decimal integer written in 12 characters from character 295 (TBCOL19).' - id: 'gap_20' type: str size: 1 doc: 'Gap: Characters before column 20 that no column uses.' - id: 'dezero' type: str size: 15 doc: 'DEZERO: Column 20 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM20 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 308 (TBCOL20).' - id: 'gap_21' type: str size: 1 doc: 'Gap: Characters before column 21 that no column uses.' - id: 'biaseven' type: str size: 15 doc: 'BIASEVEN: Column 21 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM21 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 324 (TBCOL21).' - id: 'gap_22' type: str size: 1 doc: 'Gap: Characters before column 22 that no column uses.' - id: 'biasodd' type: str size: 15 doc: 'BIASODD: Column 22 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM22 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 340 (TBCOL22).' - id: 'gap_23' type: str size: 1 doc: 'Gap: Characters before column 23 that no column uses.' - id: 'goodmin' type: str size: 15 doc: 'GOODMIN: Column 23 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM23 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 356 (TBCOL23).' - id: 'gap_24' type: str size: 1 doc: 'Gap: Characters before column 24 that no column uses.' - id: 'goodmax' type: str size: 15 doc: 'GOODMAX: Column 24 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM24 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 372 (TBCOL24).' - id: 'gap_25' type: str size: 1 doc: 'Gap: Characters before column 25 that no column uses.' - id: 'datamean' type: str size: 15 doc: 'DATAMEAN: Column 25 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM25 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 388 (TBCOL25).' - id: 'gap_26' type: str size: 1 doc: 'Gap: Characters before column 26 that no column uses.' - id: 'gpixels' type: str size: 12 doc: 'GPIXELS: Column 26 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM26 = ''I12'', a decimal integer written in 12 characters from character 404 (TBCOL26).' - id: 'gap_27' type: str size: 1 doc: 'Gap: Characters before column 27 that no column uses.' - id: 'softerrs' type: str size: 12 doc: 'SOFTERRS: Column 27 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM27 = ''I12'', a decimal integer written in 12 characters from character 417 (TBCOL27).' - id: 'gap_28' type: str size: 1 doc: 'Gap: Characters before column 28 that no column uses.' - id: 'calibdef' type: str size: 12 doc: 'CALIBDEF: Column 28 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM28 = ''I12'', a decimal integer written in 12 characters from character 430 (TBCOL28).' - id: 'gap_29' type: str size: 1 doc: 'Gap: Characters before column 29 that no column uses.' - id: 'staticd' type: str size: 12 doc: 'STATICD: Column 29 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM29 = ''I12'', a decimal integer written in 12 characters from character 443 (TBCOL29).' - id: 'gap_30' type: str size: 1 doc: 'Gap: Characters before column 30 that no column uses.' - id: 'atodsat' type: str size: 12 doc: 'ATODSAT: Column 30 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM30 = ''I12'', a decimal integer written in 12 characters from character 456 (TBCOL30).' - id: 'gap_31' type: str size: 1 doc: 'Gap: Characters before column 31 that no column uses.' - id: 'datalost' type: str size: 12 doc: 'DATALOST: Column 31 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM31 = ''I12'', a decimal integer written in 12 characters from character 469 (TBCOL31).' - id: 'gap_32' type: str size: 1 doc: 'Gap: Characters before column 32 that no column uses.' - id: 'badpixel' type: str size: 12 doc: 'BADPIXEL: Column 32 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM32 = ''I12'', a decimal integer written in 12 characters from character 482 (TBCOL32).' - id: 'gap_33' type: str size: 1 doc: 'Gap: Characters before column 33 that no column uses.' - id: 'overlap' type: str size: 12 doc: 'OVERLAP: Column 33 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM33 = ''I12'', a decimal integer written in 12 characters from character 495 (TBCOL33).' - id: 'gap_34' type: str size: 1 doc: 'Gap: Characters before column 34 that no column uses.' - id: 'photmode' type: str size: 48 doc: 'PHOTMODE (CHARACTER*48): Column 34 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM34 = ''A48'', characters written in 48 characters from character 508 (TBCOL34).' - id: 'gap_35' type: str size: 1 doc: 'Gap: Characters before column 35 that no column uses.' - id: 'photflam' type: str size: 15 doc: 'PHOTFLAM: Column 35 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM35 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 557 (TBCOL35).' - id: 'gap_36' type: str size: 1 doc: 'Gap: Characters before column 36 that no column uses.' - id: 'photzpt' type: str size: 15 doc: 'PHOTZPT: Column 36 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM36 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 573 (TBCOL36).' - id: 'gap_37' type: str size: 1 doc: 'Gap: Characters before column 37 that no column uses.' - id: 'photplam' type: str size: 15 doc: 'PHOTPLAM: Column 37 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM37 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 589 (TBCOL37).' - id: 'gap_38' type: str size: 1 doc: 'Gap: Characters before column 38 that no column uses.' - id: 'photbw' type: str size: 15 doc: 'PHOTBW: Column 38 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM38 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 605 (TBCOL38).' - id: 'gap_39' type: str size: 1 doc: 'Gap: Characters before column 39 that no column uses.' - id: 'median' type: str size: 15 doc: 'MEDIAN: Column 39 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM39 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 621 (TBCOL39).' - id: 'gap_40' type: str size: 1 doc: 'Gap: Characters before column 40 that no column uses.' - id: 'medshado' type: str size: 15 doc: 'MEDSHADO: Column 40 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM40 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 637 (TBCOL40).' - id: 'gap_41' type: str size: 1 doc: 'Gap: Characters before column 41 that no column uses.' - id: 'histwide' type: str size: 15 doc: 'HISTWIDE: Column 41 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM41 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 653 (TBCOL41).' - id: 'gap_42' type: str size: 1 doc: 'Gap: Characters before column 42 that no column uses.' - id: 'skewness' type: str size: 15 doc: 'SKEWNESS: Column 42 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM42 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 669 (TBCOL42).' - id: 'gap_43' type: str size: 1 doc: 'Gap: Characters before column 43 that no column uses.' - id: 'meanc10' type: str size: 15 doc: 'MEANC10: Column 43 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM43 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 685 (TBCOL43).' - id: 'gap_44' type: str size: 1 doc: 'Gap: Characters before column 44 that no column uses.' - id: 'meanc25' type: str size: 15 doc: 'MEANC25: Column 44 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM44 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 701 (TBCOL44).' - id: 'gap_45' type: str size: 1 doc: 'Gap: Characters before column 45 that no column uses.' - id: 'meanc50' type: str size: 15 doc: 'MEANC50: Column 45 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM45 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 717 (TBCOL45).' - id: 'gap_46' type: str size: 1 doc: 'Gap: Characters before column 46 that no column uses.' - id: 'meanc100' type: str size: 15 doc: 'MEANC100: Column 46 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM46 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 733 (TBCOL46).' - id: 'gap_47' type: str size: 1 doc: 'Gap: Characters before column 47 that no column uses.' - id: 'meanc200' type: str size: 15 doc: 'MEANC200: Column 47 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM47 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 749 (TBCOL47).' - id: 'gap_48' type: str size: 1 doc: 'Gap: Characters before column 48 that no column uses.' - id: 'meanc300' type: str size: 15 doc: 'MEANC300: Column 48 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM48 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 765 (TBCOL48).' - id: 'gap_49' type: str size: 1 doc: 'Gap: Characters before column 49 that no column uses.' - id: 'backgrnd' type: str size: 15 doc: 'BACKGRND: Column 49 of HDU 2, an ASCII table (EXTNAME ''u5780205r_cvt.c0h.tab'') of 4 rows of 49 columns: TFORM49 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 781 (TBCOL49).' - id: 'spare' type: str size: 1 doc: 'Spare: Characters at the end of each row that no column uses.'

Linked from