FITS file FOCx38i0101t_c0f.fits: Kaitai Struct description

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

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 FOCx38i0101t_c0f.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file FOCx38i0101t_c0f.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_focx38i0101t_c0f_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 1024 x 1024 array hdu2: HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 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 1024 x 1024 array: The header of HDU 1, the primary HDU, a 1024 x 1024 array: 135 keyword records of 80 ASCII characters, the last END, in 4 blocks.' - id: 'hdu1_image' type: 'hdu1_image' repeat: expr repeat-expr: 1024 doc: 'Image row: One row of the 1024 x 1024 array of HDU 1, the primary HDU, a 1024 x 1024 array: 1024 pixels along axis 1.' - id: 'hdu1_fill' size: 1856 doc: 'Fill: Fill after the data of HDU 1, the primary HDU, a 1024 x 1024 array, to a whole number of 2880-byte blocks.' - id: 'hdu2_header' type: 'hdu2_header' doc: 'Header of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: The header of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: 83 keyword records of 80 ASCII characters, the last END, in 3 blocks.' - id: 'hdu2_row' type: 'hdu2_row' repeat: expr repeat-expr: 1 doc: 'Table row: One of the 1 rows of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns, 312 characters (NAXIS1).' - id: 'hdu2_fill' size: 2568 doc: 'Fill: Fill after the data of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, a 1024 x 1024 array: The header of HDU 1, the primary HDU, a 1024 x 1024 array: 135 keyword records of 80 ASCII characters, the last END, in 4 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: "Standard FITS format"' 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: "32 bit IEEE floating point numbers"' 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 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.' 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.' 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: "There may be standard extensions"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTEND' - 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: "Institution that originated the FITS file"' 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 GEIS header file name with _cvt"' - id: 'odattype' type: str size: 80 doc: 'ODATTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Original datatype"' - id: 'sdasmgnu' type: str size: 80 doc: 'SDASMGNU: A keyword the FITS Standard doesn''t define. This record''s comment: "GCOUNT of original image"' - id: 'dadsfile' type: str size: 80 doc: 'DADSFILE: A keyword the FITS Standard doesn''t define.' - id: 'dadsclas' type: str size: 80 doc: 'DADSCLAS: A keyword the FITS Standard doesn''t define.' - id: 'dadsdate' type: str size: 80 doc: 'DADSDATE: A keyword the FITS Standard doesn''t define.' - 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: 'blank' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_2' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_3' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: '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: '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: "instrument in use"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - 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: 'filetype' type: str size: 80 doc: 'FILETYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "shp, sdq, udl, sci"' - 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: 'kxdeploy' type: str size: 80 doc: 'KXDEPLOY: A keyword the FITS Standard doesn''t define. This record''s comment: "COSTAR deployed for FOC (T or F)"' - id: 'optcrly' type: str size: 80 doc: 'OPTCRLY: A keyword the FITS Standard doesn''t define. This record''s comment: "optical relay: F48, F96"' - id: 'cammode' type: str size: 80 doc: 'CAMMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "coronographic apodizer mask: INBEAM, NOTUSED"' - id: 'f_ratio' type: str size: 80 doc: 'F_RATIO: A keyword the FITS Standard doesn''t define. This record''s comment: "focal ratio"' - id: 'smmmode' type: str size: 80 doc: 'SMMMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "spectro. mirror mechanism: INBEAM, NOTUSED"' - id: 'shtmode' type: str size: 80 doc: 'SHTMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "shutter mode: INBEAM, NOTUSED"' - id: 'ledmode' type: str size: 80 doc: 'LEDMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "led calibration status: ACTIVE, NOTUSED"' - id: 'pxformt' type: str size: 80 doc: 'PXFORMT: A keyword the FITS Standard doesn''t define. This record''s comment: "format of the image: NORMAL, ZOOM"' - id: 'optelt1' type: str size: 80 doc: 'OPTELT1: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element, wheel 1 f48: (0-7), f96: (0-11)"' - id: 'optelt2' type: str size: 80 doc: 'OPTELT2: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element, wheel 2 f48: (0-7), f96: (0-11)"' - id: 'optelt3' type: str size: 80 doc: 'OPTELT3: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element, wheel 3 f48: (0), f96: (0-11)"' - id: 'optelt4' type: str size: 80 doc: 'OPTELT4: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element, wheel 4 f48: (0), f96: (0-11)"' - id: 'filtnam1' type: str size: 80 doc: 'FILTNAM1: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element name for wheel 1"' - id: 'filtnam2' type: str size: 80 doc: 'FILTNAM2: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element name for wheel 2"' - id: 'filtnam3' type: str size: 80 doc: 'FILTNAM3: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element name for wheel 3"' - id: 'filtnam4' type: str size: 80 doc: 'FILTNAM4: A keyword the FITS Standard doesn''t define. This record''s comment: "filter element name for wheel 4"' - id: 'sampoff' type: str size: 80 doc: 'SAMPOFF: A keyword the FITS Standard doesn''t define. This record''s comment: "sample offset (0.0-1023.75)"' - id: 'lineoff' type: str size: 80 doc: 'LINEOFF: A keyword the FITS Standard doesn''t define. This record''s comment: "line offset (0.0-1023.75)"' - id: 'samppln' type: str size: 80 doc: 'SAMPPLN: A keyword the FITS Standard doesn''t define. This record''s comment: "samples per line (64, 128, 256, or 512)"' - id: 'linepfm' type: str size: 80 doc: 'LINEPFM: A keyword the FITS Standard doesn''t define. This record''s comment: "lines per frame (64, 128, 256, 512, or 1024)"' - 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: '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: '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: 'unitab' type: str size: 80 doc: 'UNITAB: A keyword the FITS Standard doesn''t define. This record''s comment: "table of reciprocal flat field filenames"' - id: 'bachfile' type: str size: 80 doc: 'BACHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "background reference header file"' - id: 'itfhfile' type: str size: 80 doc: 'ITFHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "itf reference header file"' - id: 'blmhfile' type: str size: 80 doc: 'BLMHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "blemish header file"' - id: 'unihfile' type: str size: 80 doc: 'UNIHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "uniform de reference header file"' - id: 'sdehfile' type: str size: 80 doc: 'SDEHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "sde reference header file"' - id: 'geohfile' type: str size: 80 doc: 'GEOHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "geometric reference header file"' - 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: 'baccorr' type: str size: 80 doc: 'BACCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "background subtraction correction"' - id: 'itfcorr' type: str size: 80 doc: 'ITFCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "intensity transfer function correction"' - id: 'pxlcorr' type: str size: 80 doc: 'PXLCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "split zoom-format pixels"' - id: 'unicorr' type: str size: 80 doc: 'UNICORR: A keyword the FITS Standard doesn''t define. This record''s comment: "uniform de correction"' - id: 'wavcorr' type: str size: 80 doc: 'WAVCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "compute photometric parameters"' - id: 'geocorr' type: str size: 80 doc: 'GEOCORR: A keyword the FITS Standard doesn''t define. This record''s comment: "geometric correction"' - id: 'sdecorr' type: str size: 80 doc: 'SDECORR: A keyword the FITS Standard doesn''t define. This record''s comment: "spectrograph de correction"' - 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: 'dnformt' type: str size: 80 doc: 'DNFORMT: A keyword the FITS Standard doesn''t define. This record''s comment: "bits in each data number (8/16)"' - id: 'geodefv' type: str size: 80 doc: 'GEODEFV: A keyword the FITS Standard doesn''t define. This record''s comment: "geo DN value for areas outside sci image"' - 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: 'blank_14' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'date' type: str size: 80 doc: 'DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record''s comment: "date this file originated (dd/mm/yy)"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE' - 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: '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: 'ledcolor' type: str size: 80 doc: 'LEDCOLOR: A keyword the FITS Standard doesn''t define. This record''s comment: "LED color (a color, blank , NONE or ERROR)"' - 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: '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. This record''s comment: "Inverse Sensitivity"' - id: 'photzpt' type: str size: 80 doc: 'PHOTZPT: A keyword the FITS Standard doesn''t define. This record''s comment: "ST magnitude zero point"' - id: 'photplam' type: str size: 80 doc: 'PHOTPLAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Pivot wavelength"' - id: 'photbw' type: str size: 80 doc: 'PHOTBW: A keyword the FITS Standard doesn''t define. This record''s comment: "RMS Bandwidth of the Filter and Detector"' - id: 'blank_19' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_20' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: '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 the celestial coordinate system"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - 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 (deg)"' - 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 (deg)"' - 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 (deg)"' - 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_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: '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 (dd/mm/yy)"' 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_22' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'blank_23' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'targname' type: str size: 80 doc: 'TARGNAME: A keyword the FITS Standard doesn''t define. This record''s comment: "proposer''s target name"' - id: 'ra_targ' type: str size: 80 doc: 'RA_TARG: A keyword the FITS Standard doesn''t define. This record''s comment: "right ascension of the target (deg) (J2000)"' - id: 'dec_targ' type: str size: 80 doc: 'DEC_TARG: A keyword the FITS Standard doesn''t define. This record''s comment: "declination of the target (deg) (J2000)"' - id: 'blank_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: '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: '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: '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: '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: 720 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 1024 x 1024 array of HDU 1, the primary HDU, a 1024 x 1024 array: 1024 pixels along axis 1.' seq: - id: 'pixel' type: f4 repeat: expr repeat-expr: 1024 doc: 'Pixel value: The values of the 1024 x 1024 array of HDU 1, the primary HDU, a 1024 x 1024 array, IEEE single-precision floating point (BITPIX = -32), one row of 1024 values per "hdu1_image" record. Axis 1: RA---TAN. Axis 2: DEC--TAN.' 'hdu2_header': doc: 'Header of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: The header of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: 83 keyword records of 80 ASCII characters, the last END, in 3 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: "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: "Printable ASCII characters"' 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: "GCOUNT of original file"' 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 parameter"' 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: "PCOUNT of original file"' 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: "GEIS header file name with .tab"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - 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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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: 'mir_revr' type: str size: 80 doc: 'MIR_REVR: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: '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: 'orientat' type: str size: 80 doc: 'ORIENTAT: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: 'fillcnt' type: str size: 80 doc: 'FILLCNT: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: 'errcnt' type: str size: 80 doc: 'ERRCNT: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: 'fpkttime' type: str size: 80 doc: 'FPKTTIME: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: 'lpkttime' type: str size: 80 doc: 'LPKTTIME: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: '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: '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: '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: '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: '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: '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: '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: '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.' 'hdu2_row': doc: 'Table row: One of the 1 rows of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns, 312 characters (NAXIS1).' seq: - id: 'crval1' type: str size: 25 doc: 'CRVAL1: Column 1 of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM1 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 1 (TBCOL1).' - id: 'gap_2' type: str size: 3 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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM2 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 29 (TBCOL2).' - id: 'gap_3' type: str size: 3 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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM3 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 57 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM4 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 73 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM5 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 89 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM6 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 105 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM7 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 121 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM8 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 137 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM9 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 153 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM10 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 169 (TBCOL10).' - id: 'gap_11' type: str size: 1 doc: 'Gap: Characters before column 11 that no column uses.' - id: 'mir_revr' type: str size: 4 doc: 'MIR_REVR (LOGICAL-): Column 11 of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM11 = ''A4'', characters written in 4 characters from character 185 (TBCOL11).' - id: 'gap_12' type: str size: 4 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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM12 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 193 (TBCOL12).' - id: 'gap_13' type: str size: 1 doc: 'Gap: Characters before column 13 that no column uses.' - id: 'fillcnt' type: str size: 11 doc: 'FILLCNT: Column 13 of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM13 = ''I11'', a decimal integer written in 11 characters from character 209 (TBCOL13).' - id: 'gap_14' type: str size: 1 doc: 'Gap: Characters before column 14 that no column uses.' - id: 'errcnt' type: str size: 11 doc: 'ERRCNT: Column 14 of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM14 = ''I11'', a decimal integer written in 11 characters from character 221 (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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM15 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 233 (TBCOL15).' - id: 'gap_16' type: str size: 3 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 ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM16 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 261 (TBCOL16).' - id: 'gap_17' type: str size: 3 doc: 'Gap: Characters before column 17 that no column uses.' - id: 'ctype1' type: str size: 8 doc: 'CTYPE1: Column 17 of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM17 = ''A8'', characters written in 8 characters from character 289 (TBCOL17).' - id: 'gap_18' type: str size: 4 doc: 'Gap: Characters before column 18 that no column uses.' - id: 'ctype2' type: str size: 8 doc: 'CTYPE2: Column 18 of HDU 2, an ASCII table (EXTNAME ''x38i0101t.c0h.tab'') of 1 row of 18 columns: TFORM18 = ''A8'', characters written in 8 characters from character 301 (TBCOL18).' - id: 'spare' type: str size: 4 doc: 'Spare: Characters at the end of each row that no column uses.'

Linked from