FITS file FOSy19g0309t_c2f.fits: Kaitai Struct description

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

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 FOSy19g0309t_c2f.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file FOSy19g0309t_c2f.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_fosy19g0309t_c2f_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 2064 x 2 array hdu2: HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 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 2064 x 2 array: The header of HDU 1, the primary HDU, a 2064 x 2 array: 164 keyword records of 80 ASCII characters, the last END, in 5 blocks.' - id: 'hdu1_image' type: 'hdu1_image' repeat: expr repeat-expr: 2 doc: 'Image row: One row of the 2064 x 2 array of HDU 1, the primary HDU, a 2064 x 2 array: 2064 pixels along axis 1.' - id: 'hdu1_fill' size: 768 doc: 'Fill: Fill after the data of HDU 1, the primary HDU, a 2064 x 2 array, to a whole number of 2880-byte blocks.' - id: 'hdu2_header' type: 'hdu2_header' doc: 'Header of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: The header of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: 86 keyword records of 80 ASCII characters, the last END, in 3 blocks.' - id: 'hdu2_row' type: 'hdu2_row' repeat: expr repeat-expr: 2 doc: 'Table row: One of the 2 rows of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns, 336 characters (NAXIS1).' - id: 'hdu2_fill' size: 2208 doc: 'Fill: Fill after the data of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, a 2064 x 2 array: The header of HDU 1, the primary HDU, a 2064 x 2 array: 164 keyword records of 80 ASCII characters, the last END, in 5 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: '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: '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: '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: 'ra_aper' type: str size: 80 doc: 'RA_APER: A keyword the FITS Standard doesn''t define.' - id: 'dec_aper' type: str size: 80 doc: 'DEC_APER: 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: 'aper_pos' type: str size: 80 doc: 'APER_POS: A keyword the FITS Standard doesn''t define.' - id: 'pass_dir' type: str size: 80 doc: 'PASS_DIR: A keyword the FITS Standard doesn''t define.' - id: 'ypos' type: str size: 80 doc: 'YPOS: A keyword the FITS Standard doesn''t define.' - id: 'ytype' type: str size: 80 doc: 'YTYPE: A keyword the FITS Standard doesn''t define.' - id: 'exposure' type: str size: 80 doc: 'EXPOSURE: A keyword the FITS Standard doesn''t define.' - id: 'x_offset' type: str size: 80 doc: 'X_OFFSET: A keyword the FITS Standard doesn''t define.' - id: 'y_offset' type: str size: 80 doc: 'Y_OFFSET: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: "file type"' - id: 'bunit' type: str size: 80 doc: 'BUNIT: The value field shall contain a character string describing the physical units in which the quantities in the array, after application of BSCALE and BZERO, are expressed. These units must follow the prescriptions of Sect. 4.3. This record''s comment: "brightness units"' doc-ref: 'http://ontology.oais.info/fits/keyword/BUNIT' - 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: 'header' type: str size: 80 doc: 'HEADER: A keyword the FITS Standard doesn''t define. This record''s comment: "science header line exists"' - id: 'trailer' type: str size: 80 doc: 'TRAILER: A keyword the FITS Standard doesn''t define. This record''s comment: "reject array exists"' - id: 'ywrdslin' type: str size: 80 doc: 'YWRDSLIN: A keyword the FITS Standard doesn''t define. This record''s comment: "science words per packet"' - id: 'ylinsfrm' type: str size: 80 doc: 'YLINSFRM: A keyword the FITS Standard doesn''t define. This record''s comment: "packets per frame"' - 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: 'grndmode' type: str size: 80 doc: 'GRNDMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "ground software mode"' - id: 'detector' type: str size: 80 doc: 'DETECTOR: A keyword the FITS Standard doesn''t define. This record''s comment: "detector in use: amber, blue"' - id: 'aper_id' type: str size: 80 doc: 'APER_ID: A keyword the FITS Standard doesn''t define. This record''s comment: "aperture id"' - id: 'polar_id' type: str size: 80 doc: 'POLAR_ID: A keyword the FITS Standard doesn''t define. This record''s comment: "polarizer id"' - id: 'polang' type: str size: 80 doc: 'POLANG: A keyword the FITS Standard doesn''t define. This record''s comment: "initial angular position of polarizer"' - id: 'fgwa_id' type: str size: 80 doc: 'FGWA_ID: A keyword the FITS Standard doesn''t define. This record''s comment: "FGWA id"' - id: 'fchnl' type: str size: 80 doc: 'FCHNL: A keyword the FITS Standard doesn''t define. This record''s comment: "first channel"' - id: 'nchnls' type: str size: 80 doc: 'NCHNLS: A keyword the FITS Standard doesn''t define. This record''s comment: "number of channels"' - id: 'overscan' type: str size: 80 doc: 'OVERSCAN: A keyword the FITS Standard doesn''t define. This record''s comment: "overscan number"' - id: 'nxsteps' type: str size: 80 doc: 'NXSTEPS: A keyword the FITS Standard doesn''t define. This record''s comment: "number of x steps"' - id: 'yfgimpen' type: str size: 80 doc: 'YFGIMPEN: A keyword the FITS Standard doesn''t define. This record''s comment: "onboard GIMP correction enabled (T/F)"' - id: 'yfgimper' type: str size: 80 doc: 'YFGIMPER: A keyword the FITS Standard doesn''t define. This record''s comment: "error in onboard GIMP correction (YES/NO)"' - 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: 'defddtbl' type: str size: 80 doc: 'DEFDDTBL: A keyword the FITS Standard doesn''t define. This record''s comment: "UDL disabled diode table used"' - id: 'bachfile' type: str size: 80 doc: 'BACHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "background header file"' - id: 'fl1hfile' type: str size: 80 doc: 'FL1HFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "first flat-field header file"' - id: 'fl2hfile' type: str size: 80 doc: 'FL2HFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "second flat-field header file"' - id: 'iv1hfile' type: str size: 80 doc: 'IV1HFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "first inverse sensitivity header file"' - id: 'iv2hfile' type: str size: 80 doc: 'IV2HFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "second inverse sensitivity header file"' - id: 'rethfile' type: str size: 80 doc: 'RETHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "waveplate retardation header file"' - id: 'ddthfile' type: str size: 80 doc: 'DDTHFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "disabled diode table header file"' - id: 'dq1hfile' type: str size: 80 doc: 'DQ1HFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "first data quality initialization header file"' - id: 'dq2hfile' type: str size: 80 doc: 'DQ2HFILE: A keyword the FITS Standard doesn''t define. This record''s comment: "second data quality initialization header file"' - id: 'ccg2' type: str size: 80 doc: 'CCG2: A keyword the FITS Standard doesn''t define. This record''s comment: "paired pulse correction parameters"' - id: 'ccs0' type: str size: 80 doc: 'CCS0: A keyword the FITS Standard doesn''t define. This record''s comment: "aperture parameters"' - id: 'ccs1' type: str size: 80 doc: 'CCS1: A keyword the FITS Standard doesn''t define. This record''s comment: "aperture position parameters"' - id: 'ccs2' type: str size: 80 doc: 'CCS2: A keyword the FITS Standard doesn''t define. This record''s comment: "sky emission line regions"' - id: 'ccs3' type: str size: 80 doc: 'CCS3: A keyword the FITS Standard doesn''t define. This record''s comment: "big and sky filter widths and prism X0"' - id: 'ccs4' type: str size: 80 doc: 'CCS4: A keyword the FITS Standard doesn''t define. This record''s comment: "polarimetry parameters"' - id: 'ccs5' type: str size: 80 doc: 'CCS5: A keyword the FITS Standard doesn''t define. This record''s comment: "sky shifts"' - id: 'ccs6' type: str size: 80 doc: 'CCS6: A keyword the FITS Standard doesn''t define. This record''s comment: "wavelength coefficients"' - id: 'ccs7' type: str size: 80 doc: 'CCS7: A keyword the FITS Standard doesn''t define. This record''s comment: "GIMP correction scale factores"' - id: 'ccs8' type: str size: 80 doc: 'CCS8: A keyword the FITS Standard doesn''t define. This record''s comment: "predicted background count rates"' - 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: 'cnt_corr' type: str size: 80 doc: 'CNT_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "count to count rate conversion"' - id: 'off_corr' type: str size: 80 doc: 'OFF_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "GIMP correction"' - id: 'ppc_corr' type: str size: 80 doc: 'PPC_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "paired pulse correction"' - id: 'bac_corr' type: str size: 80 doc: 'BAC_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "background subtraction"' - id: 'gmf_corr' type: str size: 80 doc: 'GMF_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "scale reference background"' - id: 'flt_corr' type: str size: 80 doc: 'FLT_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "flat-fielding"' - id: 'sky_corr' type: str size: 80 doc: 'SKY_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "sky subtraction"' - id: 'wav_corr' type: str size: 80 doc: 'WAV_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "wavelength scale generation"' - id: 'flx_corr' type: str size: 80 doc: 'FLX_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "flux scale generation"' - id: 'err_corr' type: str size: 80 doc: 'ERR_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "propagated error computation"' - id: 'mod_corr' type: str size: 80 doc: 'MOD_CORR: A keyword the FITS Standard doesn''t define. This record''s comment: "ground software mode dependent reductions"' - 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: 'ints' type: str size: 80 doc: 'INTS: A keyword the FITS Standard doesn''t define. This record''s comment: "number of integrations"' - id: 'ybase' type: str size: 80 doc: 'YBASE: A keyword the FITS Standard doesn''t define. This record''s comment: "y base"' - id: 'yrange' type: str size: 80 doc: 'YRANGE: A keyword the FITS Standard doesn''t define. This record''s comment: "y range"' - id: 'ysteps' type: str size: 80 doc: 'YSTEPS: A keyword the FITS Standard doesn''t define. This record''s comment: "number of y steps"' - id: 'yspace' type: str size: 80 doc: 'YSPACE: A keyword the FITS Standard doesn''t define. This record''s comment: "yrange * 32 / ysteps"' - id: 'slices' type: str size: 80 doc: 'SLICES: A keyword the FITS Standard doesn''t define. This record''s comment: "number of time slices"' - id: 'npat' type: str size: 80 doc: 'NPAT: A keyword the FITS Standard doesn''t define. This record''s comment: "number of patterns per readout"' - id: 'nread' type: str size: 80 doc: 'NREAD: A keyword the FITS Standard doesn''t define. This record''s comment: "number of readouts per memory clear"' - id: 'nmclears' type: str size: 80 doc: 'NMCLEARS: A keyword the FITS Standard doesn''t define. This record''s comment: "number of memory clears per acquisition"' - id: 'ystep1' type: str size: 80 doc: 'YSTEP1: A keyword the FITS Standard doesn''t define. This record''s comment: "first ystep data type: OBJ, SKY, BCK, NUL"' - id: 'ystep2' type: str size: 80 doc: 'YSTEP2: A keyword the FITS Standard doesn''t define. This record''s comment: "second ystep data type: OBJ, SKY, BCK, NUL"' - id: 'ystep3' type: str size: 80 doc: 'YSTEP3: A keyword the FITS Standard doesn''t define. This record''s comment: "third ystep data type: OBJ, SKY, BCK, NUL"' - id: 'xbase' type: str size: 80 doc: 'XBASE: A keyword the FITS Standard doesn''t define. This record''s comment: "X-deflection base"' - id: 'xpitch' type: str size: 80 doc: 'XPITCH: A keyword the FITS Standard doesn''t define. This record''s comment: "X-deflection pitch between diode"' - id: 'ypitch' type: str size: 80 doc: 'YPITCH: A keyword the FITS Standard doesn''t define. This record''s comment: "Y-deflection pitch"' - 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: 'livetime' type: str size: 80 doc: 'LIVETIME: A keyword the FITS Standard doesn''t define. This record''s comment: "accumulator open time (unit=7.8125 microsec)"' - id: 'deadtime' type: str size: 80 doc: 'DEADTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "accumulator close time (unit=7.8125 microsec)"' - id: 'maxclk' type: str size: 80 doc: 'MAXCLK: A keyword the FITS Standard doesn''t define. This record''s comment: "maximum clock count"' - id: 'pa_aper' type: str size: 80 doc: 'PA_APER: A keyword the FITS Standard doesn''t define. This record''s comment: "position ang of aperture used with target (deg)"' - id: 'noiselm' type: str size: 80 doc: 'NOISELM: A keyword the FITS Standard doesn''t define. This record''s comment: "burst noise rejection limit"' - id: 'offs_tab' type: str size: 80 doc: 'OFFS_TAB: A keyword the FITS Standard doesn''t define. This record''s comment: "GIMP offsets (post-pipeline processing only)"' - id: 'minwave' type: str size: 80 doc: 'MINWAVE: A keyword the FITS Standard doesn''t define. This record''s comment: "minimum wavelength (angstroms)"' - id: 'maxwave' type: str size: 80 doc: 'MAXWAVE: A keyword the FITS Standard doesn''t define. This record''s comment: "maximum wavelength (angstroms)"' - 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: 'date' type: str size: 80 doc: 'DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record''s comment: "date this file was written (dd/mm/yy)"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE' - id: 'pktfmt' type: str size: 80 doc: 'PKTFMT: A keyword the FITS Standard doesn''t define. This record''s comment: "packet format code"' - 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_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: 'ra_aper1' type: str size: 80 doc: 'RA_APER1: A keyword the FITS Standard doesn''t define. This record''s comment: "right ascension of the aperture (deg)"' - id: 'decaper1' type: str size: 80 doc: 'DECAPER1: A keyword the FITS Standard doesn''t define. This record''s comment: "declination of the aperture (deg)"' - 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: '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_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: '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_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: '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_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: '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_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: '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: 1280 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 2064 x 2 array of HDU 1, the primary HDU, a 2064 x 2 array: 2064 pixels along axis 1.' seq: - id: 'pixel' type: f4 repeat: expr repeat-expr: 2064 doc: 'Pixel value (ERGS/CM**2/S/A): The values of the 2064 x 2 array of HDU 1, the primary HDU, a 2064 x 2 array, IEEE single-precision floating point (BITPIX = -32), one row of 2064 values per "hdu1_image" record. Axis 1: PIXEL.' 'hdu2_header': doc: 'Header of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: The header of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: 86 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: '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: '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: '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: '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: '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: '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: '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: '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: 'ra_aper' type: str size: 80 doc: 'RA_APER: A keyword the FITS Standard doesn''t define.' - 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: 'dec_aper' type: str size: 80 doc: 'DEC_APER: A keyword the FITS Standard doesn''t define.' - 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: 'fillcnt' type: str size: 80 doc: 'FILLCNT: A keyword the FITS Standard doesn''t define.' - 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: 'errcnt' type: str size: 80 doc: 'ERRCNT: A keyword the FITS Standard doesn''t define.' - 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: 'fpkttime' type: str size: 80 doc: 'FPKTTIME: A keyword the FITS Standard doesn''t define.' - 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: 'lpkttime' type: str size: 80 doc: 'LPKTTIME: 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: '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: '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: '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: 'aper_pos' type: str size: 80 doc: 'APER_POS: 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: 'pass_dir' type: str size: 80 doc: 'PASS_DIR: 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: 'ypos' type: str size: 80 doc: 'YPOS: 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: 'ytype' type: str size: 80 doc: 'YTYPE: 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: 'exposure' type: str size: 80 doc: 'EXPOSURE: A keyword the FITS Standard doesn''t define.' - 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: 'x_offset' type: str size: 80 doc: 'X_OFFSET: A keyword the FITS Standard doesn''t define.' - 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: '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: 'y_offset' type: str size: 80 doc: 'Y_OFFSET: A keyword the FITS Standard doesn''t define.' - 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: '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: '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: 1760 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 2 rows of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns, 336 characters (NAXIS1).' seq: - id: 'crval1' type: str size: 25 doc: 'CRVAL1: Column 1 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 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: 'crpix1' type: str size: 15 doc: 'CRPIX1: Column 2 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM2 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 29 (TBCOL2).' - id: 'gap_3' type: str size: 1 doc: 'Gap: Characters before column 3 that no column uses.' - id: 'cd1_1' type: str size: 15 doc: 'CD1_1: Column 3 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM3 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 45 (TBCOL3).' - id: 'gap_4' type: str size: 1 doc: 'Gap: Characters before column 4 that no column uses.' - id: 'datamin' type: str size: 15 doc: 'DATAMIN: Column 4 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM4 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 61 (TBCOL4).' - id: 'gap_5' type: str size: 1 doc: 'Gap: Characters before column 5 that no column uses.' - id: 'datamax' type: str size: 15 doc: 'DATAMAX: Column 5 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM5 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 77 (TBCOL5).' - id: 'gap_6' type: str size: 1 doc: 'Gap: Characters before column 6 that no column uses.' - id: 'ra_aper' type: str size: 25 doc: 'RA_APER: Column 6 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM6 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 93 (TBCOL6).' - id: 'gap_7' type: str size: 3 doc: 'Gap: Characters before column 7 that no column uses.' - id: 'dec_aper' type: str size: 25 doc: 'DEC_APER: Column 7 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM7 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 121 (TBCOL7).' - id: 'gap_8' type: str size: 3 doc: 'Gap: Characters before column 8 that no column uses.' - id: 'fillcnt' type: str size: 11 doc: 'FILLCNT: Column 8 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM8 = ''I11'', a decimal integer written in 11 characters from character 149 (TBCOL8).' - id: 'gap_9' type: str size: 1 doc: 'Gap: Characters before column 9 that no column uses.' - id: 'errcnt' type: str size: 11 doc: 'ERRCNT: Column 9 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM9 = ''I11'', a decimal integer written in 11 characters from character 161 (TBCOL9).' - id: 'gap_10' type: str size: 1 doc: 'Gap: Characters before column 10 that no column uses.' - id: 'fpkttime' type: str size: 25 doc: 'FPKTTIME: Column 10 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM10 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 173 (TBCOL10).' - id: 'gap_11' type: str size: 3 doc: 'Gap: Characters before column 11 that no column uses.' - id: 'lpkttime' type: str size: 25 doc: 'LPKTTIME: Column 11 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM11 = ''D25.16'', a decimal number with an exponent written in 25 characters from character 201 (TBCOL11).' - id: 'gap_12' type: str size: 3 doc: 'Gap: Characters before column 12 that no column uses.' - id: 'ctype1' type: str size: 8 doc: 'CTYPE1: Column 12 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM12 = ''A8'', characters written in 8 characters from character 229 (TBCOL12).' - id: 'gap_13' type: str size: 4 doc: 'Gap: Characters before column 13 that no column uses.' - id: 'aper_pos' type: str size: 8 doc: 'APER_POS: Column 13 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM13 = ''A8'', characters written in 8 characters from character 241 (TBCOL13).' - id: 'gap_14' type: str size: 4 doc: 'Gap: Characters before column 14 that no column uses.' - id: 'pass_dir' type: str size: 11 doc: 'PASS_DIR: Column 14 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM14 = ''I11'', a decimal integer written in 11 characters from character 253 (TBCOL14).' - id: 'gap_15' type: str size: 1 doc: 'Gap: Characters before column 15 that no column uses.' - id: 'ypos' type: str size: 15 doc: 'YPOS: Column 15 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM15 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 265 (TBCOL15).' - id: 'gap_16' type: str size: 1 doc: 'Gap: Characters before column 16 that no column uses.' - id: 'ytype' type: str size: 4 doc: 'YTYPE: Column 16 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM16 = ''A4'', characters written in 4 characters from character 281 (TBCOL16).' - id: 'gap_17' type: str size: 4 doc: 'Gap: Characters before column 17 that no column uses.' - id: 'exposure' type: str size: 15 doc: 'EXPOSURE: Column 17 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM17 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 289 (TBCOL17).' - id: 'gap_18' type: str size: 1 doc: 'Gap: Characters before column 18 that no column uses.' - id: 'x_offset' type: str size: 15 doc: 'X_OFFSET: Column 18 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM18 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 305 (TBCOL18).' - id: 'gap_19' type: str size: 1 doc: 'Gap: Characters before column 19 that no column uses.' - id: 'y_offset' type: str size: 15 doc: 'Y_OFFSET: Column 19 of HDU 2, an ASCII table (EXTNAME ''y19g0309t.c2h.tab'') of 2 rows of 19 columns: TFORM19 = ''E15.7'', a decimal number with an exponent written in 15 characters from character 321 (TBCOL19).' - id: 'spare' type: str size: 1 doc: 'Spare: Characters at the end of each row that no column uses.'

Linked from