FITS file DDTSUVDATA.fits: Kaitai Struct description

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

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 DDTSUVDATA.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file DDTSUVDATA.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_ddtsuvdata_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, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array hdu2: HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 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, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array: The header of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array: 159 keyword records of 80 ASCII characters, the last END, in 5 blocks.' - id: 'hdu1_group' type: 'hdu1_group' repeat: expr repeat-expr: 7956 doc: 'Group: One of the 7956 random groups of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array: its parameters, then its array.' - id: 'hdu1_fill' size: 288 doc: 'Fill: Fill after the data of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, to a whole number of 2880-byte blocks.' - id: 'hdu2_header' type: 'hdu2_header' doc: 'Header of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: The header of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: 61 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu2_row' type: 'hdu2_row' repeat: expr repeat-expr: 28 doc: 'Table row: One of the 28 rows of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns, 78 bytes (NAXIS1).' - id: 'hdu2_fill' size: 696 doc: 'Fill: Fill after the data of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array: The header of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array: 159 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.' 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).' 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.' 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: "No standard image just group"' 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: 'naxis3' type: str size: 80 doc: 'NAXIS3: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array.' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'naxis4' type: str size: 80 doc: 'NAXIS4: 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: 'naxis5' type: str size: 80 doc: 'NAXIS5: 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: 'naxis6' type: str size: 80 doc: 'NAXIS6: 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: "This is the antenna file"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTEND' - id: 'blocked' type: str size: 80 doc: 'BLOCKED: This keyword is deprecated and should not be used in new FITS files. It is reserved primarily to prevent its use with other meanings. As previously defined, this keyword, if used, was required to appear only within the first 36 keywords in the primary header. This record''s comment: "Tape may be blocked"' doc-ref: 'http://ontology.oais.info/fits/keyword/BLOCKED' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed.' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header.' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'instrume' type: str size: 80 doc: 'INSTRUME: The value field shall contain a character string identifying the instrument used to acquire the data associated with the header.' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'observer' type: str size: 80 doc: 'OBSERVER: The value field shall contain a character string identifying who acquired the data associated with the header.' doc-ref: 'http://ontology.oais.info/fits/keyword/OBSERVER' - 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-OBS' - id: 'date_map' type: str size: 80 doc: 'DATE-MAP: A keyword the FITS Standard doesn''t define.' - id: 'bscale' type: str size: 80 doc: 'BSCALE: This keyword shall be used, along with the BZERO keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. This record''s comment: "REAL = TAPE * BSCALE + BZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/BSCALE' - id: 'bzero' type: str size: 80 doc: 'BZERO: This keyword shall be used, along with the BSCALE keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. The value field shall contain a floating-point number representing the physical value corresponding to an array value of zero. The default value for this keyword is 0.0.' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - id: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/BUNIT' - id: 'epoch' type: str size: 80 doc: 'EPOCH: This keyword is deprecated and should not be used in new FITS files. It is reserved primarily to prevent its use with other meanings. The EQUINOX keyword shall be used instead. The value field of this keyword was previously defined to contain a floating-point number giving the equinox in years for the celestial-coordinate system in which positions are expressed. This record''s comment: "EPOCH OF RA DEC"' doc-ref: 'http://ontology.oais.info/fits/keyword/EPOCH' - id: 'obsra' type: str size: 80 doc: 'OBSRA: A keyword the FITS Standard doesn''t define. This record''s comment: "ANTENNA POINTING RA"' - id: 'obsdec' type: str size: 80 doc: 'OBSDEC: A keyword the FITS Standard doesn''t define. This record''s comment: "ANTENNA POINTING DEC"' - 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: '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: 'cdelt2' type: str size: 80 doc: 'CDELT2: Increment of the world coordinate at the reference point for Axis i. The value must not be zero.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - 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: 'crota2' type: str size: 80 doc: 'CROTA2: The amount of rotation from the standard coordinate system to a different coordinate system. Further use of this of this keyword is deprecated, in favor of the newer formalisms that use the CDi j or PCi j keywords to define the rotation.' doc-ref: 'http://ontology.oais.info/fits/keyword/CROTAi' - id: 'ctype3' type: str size: 80 doc: 'CTYPE3: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear.' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'crval3' type: str size: 80 doc: 'CRVAL3: World-coordinate value at the reference point of Axis i.' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'cdelt3' type: str size: 80 doc: 'CDELT3: Increment of the world coordinate at the reference point for Axis i. The value must not be zero.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'crpix3' type: str size: 80 doc: 'CRPIX3: 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: 'crota3' type: str size: 80 doc: 'CROTA3: The amount of rotation from the standard coordinate system to a different coordinate system. Further use of this of this keyword is deprecated, in favor of the newer formalisms that use the CDi j or PCi j keywords to define the rotation.' doc-ref: 'http://ontology.oais.info/fits/keyword/CROTAi' - id: 'ctype4' type: str size: 80 doc: 'CTYPE4: 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: 'crval4' type: str size: 80 doc: 'CRVAL4: World-coordinate value at the reference point of Axis i.' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'cdelt4' type: str size: 80 doc: 'CDELT4: Increment of the world coordinate at the reference point for Axis i. The value must not be zero.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'crpix4' type: str size: 80 doc: 'CRPIX4: 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: 'crota4' type: str size: 80 doc: 'CROTA4: The amount of rotation from the standard coordinate system to a different coordinate system. Further use of this of this keyword is deprecated, in favor of the newer formalisms that use the CDi j or PCi j keywords to define the rotation.' doc-ref: 'http://ontology.oais.info/fits/keyword/CROTAi' - id: 'ctype5' type: str size: 80 doc: 'CTYPE5: 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: 'crval5' type: str size: 80 doc: 'CRVAL5: World-coordinate value at the reference point of Axis i.' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'cdelt5' type: str size: 80 doc: 'CDELT5: Increment of the world coordinate at the reference point for Axis i. The value must not be zero.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'crpix5' type: str size: 80 doc: 'CRPIX5: 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: 'crota5' type: str size: 80 doc: 'CROTA5: The amount of rotation from the standard coordinate system to a different coordinate system. Further use of this of this keyword is deprecated, in favor of the newer formalisms that use the CDi j or PCi j keywords to define the rotation.' doc-ref: 'http://ontology.oais.info/fits/keyword/CROTAi' - id: 'ctype6' type: str size: 80 doc: 'CTYPE6: 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: 'crval6' type: str size: 80 doc: 'CRVAL6: World-coordinate value at the reference point of Axis i.' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'cdelt6' type: str size: 80 doc: 'CDELT6: Increment of the world coordinate at the reference point for Axis i. The value must not be zero.' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'crpix6' type: str size: 80 doc: 'CRPIX6: 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: 'crota6' type: str size: 80 doc: 'CROTA6: The amount of rotation from the standard coordinate system to a different coordinate system. Further use of this of this keyword is deprecated, in favor of the newer formalisms that use the CDi j or PCi j keywords to define the rotation.' doc-ref: 'http://ontology.oais.info/fits/keyword/CROTAi' - id: 'groups' type: str size: 80 doc: 'GROUPS: The value field shall contain the logical constant T. The value T associated with this keyword implies that random-groups records are present.' doc-ref: 'http://ontology.oais.info/fits/keyword/GROUPS' - 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - 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.' doc-ref: 'http://ontology.oais.info/fits/keyword/PCOUNT' - id: 'ptype1' type: str size: 80 doc: 'PTYPE1: The value field shall contain a character string giving the name of Parameter n. If the PTYPEn keywords for more than one value of n have the same associated name in the value field, then the data value for the parameter of that name is to be obtained by adding the derived data values of the corresponding parameters.' doc-ref: 'http://ontology.oais.info/fits/keyword/PTYPEn' - id: 'pscal1' type: str size: 80 doc: 'PSCAL1: This keyword shall be used, along with the PZEROn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the true physical values it represents, using Eq. 5. The value field shall contain a floating-point number representing the coefficient of the linear term in Eq. 5, the scaling factor between true values and group parameter values at zero offset.' doc-ref: 'http://ontology.oais.info/fits/keyword/PSCALn' - id: 'pzero1' type: str size: 80 doc: 'PZERO1: This keyword shall be used, along with the PSCALn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the physical value. The value field shall contain a floating-point number, representing the true value corresponding to a group parameter value of zero. The default value for this keyword is 0.0. The transformation equation is as follows: physical value = PZEROn + PSCALn * stored value.' doc-ref: 'http://ontology.oais.info/fits/keyword/PZEROn' - id: 'ptype2' type: str size: 80 doc: 'PTYPE2: The value field shall contain a character string giving the name of Parameter n. If the PTYPEn keywords for more than one value of n have the same associated name in the value field, then the data value for the parameter of that name is to be obtained by adding the derived data values of the corresponding parameters.' doc-ref: 'http://ontology.oais.info/fits/keyword/PTYPEn' - id: 'pscal2' type: str size: 80 doc: 'PSCAL2: This keyword shall be used, along with the PZEROn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the true physical values it represents, using Eq. 5. The value field shall contain a floating-point number representing the coefficient of the linear term in Eq. 5, the scaling factor between true values and group parameter values at zero offset.' doc-ref: 'http://ontology.oais.info/fits/keyword/PSCALn' - id: 'pzero2' type: str size: 80 doc: 'PZERO2: This keyword shall be used, along with the PSCALn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the physical value. The value field shall contain a floating-point number, representing the true value corresponding to a group parameter value of zero. The default value for this keyword is 0.0. The transformation equation is as follows: physical value = PZEROn + PSCALn * stored value.' doc-ref: 'http://ontology.oais.info/fits/keyword/PZEROn' - id: 'ptype3' type: str size: 80 doc: 'PTYPE3: The value field shall contain a character string giving the name of Parameter n. If the PTYPEn keywords for more than one value of n have the same associated name in the value field, then the data value for the parameter of that name is to be obtained by adding the derived data values of the corresponding parameters.' doc-ref: 'http://ontology.oais.info/fits/keyword/PTYPEn' - id: 'pscal3' type: str size: 80 doc: 'PSCAL3: This keyword shall be used, along with the PZEROn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the true physical values it represents, using Eq. 5. The value field shall contain a floating-point number representing the coefficient of the linear term in Eq. 5, the scaling factor between true values and group parameter values at zero offset.' doc-ref: 'http://ontology.oais.info/fits/keyword/PSCALn' - id: 'pzero3' type: str size: 80 doc: 'PZERO3: This keyword shall be used, along with the PSCALn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the physical value. The value field shall contain a floating-point number, representing the true value corresponding to a group parameter value of zero. The default value for this keyword is 0.0. The transformation equation is as follows: physical value = PZEROn + PSCALn * stored value.' doc-ref: 'http://ontology.oais.info/fits/keyword/PZEROn' - id: 'ptype4' type: str size: 80 doc: 'PTYPE4: The value field shall contain a character string giving the name of Parameter n. If the PTYPEn keywords for more than one value of n have the same associated name in the value field, then the data value for the parameter of that name is to be obtained by adding the derived data values of the corresponding parameters.' doc-ref: 'http://ontology.oais.info/fits/keyword/PTYPEn' - id: 'pscal4' type: str size: 80 doc: 'PSCAL4: This keyword shall be used, along with the PZEROn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the true physical values it represents, using Eq. 5. The value field shall contain a floating-point number representing the coefficient of the linear term in Eq. 5, the scaling factor between true values and group parameter values at zero offset.' doc-ref: 'http://ontology.oais.info/fits/keyword/PSCALn' - id: 'pzero4' type: str size: 80 doc: 'PZERO4: This keyword shall be used, along with the PSCALn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the physical value. The value field shall contain a floating-point number, representing the true value corresponding to a group parameter value of zero. The default value for this keyword is 0.0. The transformation equation is as follows: physical value = PZEROn + PSCALn * stored value.' doc-ref: 'http://ontology.oais.info/fits/keyword/PZEROn' - id: 'ptype5' type: str size: 80 doc: 'PTYPE5: The value field shall contain a character string giving the name of Parameter n. If the PTYPEn keywords for more than one value of n have the same associated name in the value field, then the data value for the parameter of that name is to be obtained by adding the derived data values of the corresponding parameters.' doc-ref: 'http://ontology.oais.info/fits/keyword/PTYPEn' - id: 'pscal5' type: str size: 80 doc: 'PSCAL5: This keyword shall be used, along with the PZEROn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the true physical values it represents, using Eq. 5. The value field shall contain a floating-point number representing the coefficient of the linear term in Eq. 5, the scaling factor between true values and group parameter values at zero offset.' doc-ref: 'http://ontology.oais.info/fits/keyword/PSCALn' - id: 'pzero5' type: str size: 80 doc: 'PZERO5: This keyword shall be used, along with the PSCALn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the physical value. The value field shall contain a floating-point number, representing the true value corresponding to a group parameter value of zero. The default value for this keyword is 0.0. The transformation equation is as follows: physical value = PZEROn + PSCALn * stored value.' doc-ref: 'http://ontology.oais.info/fits/keyword/PZEROn' - id: 'ptype6' type: str size: 80 doc: 'PTYPE6: The value field shall contain a character string giving the name of Parameter n. If the PTYPEn keywords for more than one value of n have the same associated name in the value field, then the data value for the parameter of that name is to be obtained by adding the derived data values of the corresponding parameters.' doc-ref: 'http://ontology.oais.info/fits/keyword/PTYPEn' - id: 'pscal6' type: str size: 80 doc: 'PSCAL6: This keyword shall be used, along with the PZEROn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the true physical values it represents, using Eq. 5. The value field shall contain a floating-point number representing the coefficient of the linear term in Eq. 5, the scaling factor between true values and group parameter values at zero offset.' doc-ref: 'http://ontology.oais.info/fits/keyword/PSCALn' - id: 'pzero6' type: str size: 80 doc: 'PZERO6: This keyword shall be used, along with the PSCALn keyword, when the nth FITS group parameter value is not the true physical value, to transform the group parameter value to the physical value. The value field shall contain a floating-point number, representing the true value corresponding to a group parameter value of zero. The default value for this keyword is 0.0. The transformation equation is as follows: physical value = PZEROn + PSCALn * stored value.' doc-ref: 'http://ontology.oais.info/fits/keyword/PZEROn' - 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: '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: 'history_2' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_3' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_4' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_5' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_6' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_7' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_8' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_9' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_10' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_11' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_12' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_13' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_14' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_15' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_16' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_17' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_18' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_19' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_20' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_21' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_22' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_23' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_24' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_25' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_26' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_27' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_28' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_29' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_30' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_31' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_32' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_33' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_34' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_35' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_36' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_37' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_38' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_39' type: str size: 80 doc: 'HISTORY: This keyword should be used to describe the history of steps and procedures associated with the processing of the associated data. Any FITS-legal characters may appear in Bytes 9 through 80.' doc-ref: 'http://ontology.oais.info/fits/keyword/HISTORY' - id: 'history_40' 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_41' 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_42' 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_43' 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_44' 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_45' 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_46' 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_47' 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_48' 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_49' 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_50' 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_51' 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_52' 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_53' 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_54' 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_55' 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_56' 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_57' 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_58' 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_59' 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_60' 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_61' 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_62' 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_63' 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_64' 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_65' 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_66' 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_67' 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_68' 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_69' 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_70' 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_71' 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_72' 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_73' 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_74' 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_75' 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_76' 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_77' 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_78' 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_79' 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_80' 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: '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.' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'date' type: str size: 80 doc: 'DATE: The value field shall contain a character string giving the date on which the HDU was created, in the form YYYY-MM-DD, or the date and time when the HDU was created, in the form YYYY-MM-DDThh:mm:ss[.sss. . . ], where YYYY shall be the four-digit calendar year number, MM the two-digit month number with January given by 01 and December by 12, and DD the day of the month; hh:mm:ss[.sss...] is the time of day. This record''s comment: "File written on dd/mm/yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE' - id: 'history_81' 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_82' 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_83' 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: '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: 'history_84' 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: 1680 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu1_group': doc: 'Group: One of the 7956 random groups of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array: its parameters, then its array.' seq: - id: 'uu' type: f4 doc: 'UU--: Group parameter 1 of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, UU--; physical value = PZERO1 + PSCAL1 x stored value. Physical value = raw * 0.000000000704218409114 + 0.00000000000.' - id: 'vv' type: f4 doc: 'VV--: Group parameter 2 of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, VV--; physical value = PZERO2 + PSCAL2 x stored value. Physical value = raw * 0.000000000704218409114 + 0.00000000000.' - id: 'ww' type: f4 doc: 'WW--: Group parameter 3 of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, WW--; physical value = PZERO3 + PSCAL3 x stored value. Physical value = raw * 0.000000000704218409114 + 0.00000000000.' - id: 'baseline' type: f4 doc: 'BASELINE: Group parameter 4 of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, BASELINE; physical value = PZERO4 + PSCAL4 x stored value. Physical value = raw * 1.00000000000 + 0.00000000000.' - id: 'date' type: f4 doc: 'DATE: Group parameter 5 of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, DATE; physical value = PZERO5 + PSCAL5 x stored value. Physical value = raw * 1.00000000000 + 2445728.50000.' - id: 'date_2' type: f4 doc: 'DATE: Group parameter 6 of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, DATE; physical value = PZERO6 + PSCAL6 x stored value. Physical value = raw * 1.00000000000 + 0.00000000000.' - id: 'array' type: 'array' doc: 'Group array: The group''s 3 x 4 x 1 x 1 x 1 array.' 'array': doc: 'Group array: The group''s 3 x 4 x 1 x 1 x 1 array.' seq: - id: 'value' type: f4 repeat: expr repeat-expr: 12 doc: 'Array value (JY): The values of the 3 x 4 x 1 x 1 x 1 array of HDU 1, the primary HDU, random groups: 7956 groups of 6 parameters and a 3 x 4 x 1 x 1 x 1 array, IEEE single-precision floating point (BITPIX = -32), in each group. Axis 2: COMPLEX. Axis 3: STOKES. Axis 4: FREQ. Axis 5: RA. Axis 6: DEC. Physical value = BZERO + BSCALE x stored value. Physical value = raw * 1.00000000000 + 0.00000000000.' 'hdu2_header': doc: 'Header of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: The header of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: 61 keyword records of 80 ASCII characters, the last END, in 2 blocks.' seq: - id: 'xtension' type: str size: 80 doc: 'XTENSION: The value field shall contain a character string giving the name of the extension type. This keyword is mandatory for an extension header and must not appear in the primary header.7 To preclude conflict, extension type names must be registered with the IAUFWG. The current list of registered extensions is given in Appendix F. An up-to-date list is also maintained on the FITS Support Office website. This record''s comment: "Extension type"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "Binary data"' 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: "Table is a 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: "Width of table in bytes"' 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: "Number of entries in table"' 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: "Random parameter count"' 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: "Group count"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'tfields' type: str size: 80 doc: 'TFIELDS: The value field shall contain a non-negative integer representing the number of fields in each row. The maximum permissible value is 999. This record''s comment: "Number of fields in each row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - id: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "AIPS table file"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'extver' type: str size: 80 doc: 'EXTVER: The value field shall contain an integer to be used to distinguish among different extensions in a FITS file with the same type and name, i.e., the same values for XTENSION and EXTNAME. The values need not start with 1 for the first extension with a particular value of EXTNAME and need not be in sequence for subsequent values. If the EXTVER keyword is absent, the file should be treated as if the value were 1. This record''s comment: "Version number of table"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTVER' - id: 'tform1' type: str size: 80 doc: 'TFORM1: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN format of field 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'ttype1' type: str size: 80 doc: 'TTYPE1: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Type (heading) of field 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit1' type: str size: 80 doc: 'TUNIT1: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tform2' type: str size: 80 doc: 'TFORM2: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN format of field 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'ttype2' type: str size: 80 doc: 'TTYPE2: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Type (heading) of field 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit2' type: str size: 80 doc: 'TUNIT2: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tform3' type: str size: 80 doc: 'TFORM3: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN format of field 3"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'ttype3' type: str size: 80 doc: 'TTYPE3: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Type (heading) of field 3"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit3' type: str size: 80 doc: 'TUNIT3: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 3"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tform4' type: str size: 80 doc: 'TFORM4: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN format of field 4"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'ttype4' type: str size: 80 doc: 'TTYPE4: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Type (heading) of field 4"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit4' type: str size: 80 doc: 'TUNIT4: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 4"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tform5' type: str size: 80 doc: 'TFORM5: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN format of field 5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'ttype5' type: str size: 80 doc: 'TTYPE5: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Type (heading) of field 5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit5' type: str size: 80 doc: 'TUNIT5: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tform6' type: str size: 80 doc: 'TFORM6: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding. This record''s comment: "FORTRAN format of field 6"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'ttype6' type: str size: 80 doc: 'TTYPE6: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Type (heading) of field 6"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit6' type: str size: 80 doc: 'TUNIT6: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 6"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - 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. This record''s comment: "FORTRAN format of field 7"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - 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. This record''s comment: "Type (heading) of field 7"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit7' type: str size: 80 doc: 'TUNIT7: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 7"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - 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. This record''s comment: "FORTRAN format of field 8"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - 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. This record''s comment: "Type (heading) of field 8"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit8' type: str size: 80 doc: 'TUNIT8: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 8"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - 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. This record''s comment: "FORTRAN format of field 9"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - 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. This record''s comment: "Type (heading) of field 9"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit9' type: str size: 80 doc: 'TUNIT9: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "Physical units of field 9"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - 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. This record''s comment: "FORTRAN format of field 10"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - 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. This record''s comment: "Type (heading) of field 10"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit10' type: str size: 80 doc: 'TUNIT10: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of field 10"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - 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. This record''s comment: "FORTRAN format of field 11"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - 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. This record''s comment: "Type (heading) of field 11"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - 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. This record''s comment: "physical units of field 11"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - 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. This record''s comment: "FORTRAN format of field 12"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - 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. This record''s comment: "Type (heading) of field 12"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tunit12' type: str size: 80 doc: 'TUNIT12: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3. This record''s comment: "physical units of field 12"' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'arrayx' type: str size: 80 doc: 'ARRAYX: A keyword the FITS Standard doesn''t define.' - id: 'arrayy' type: str size: 80 doc: 'ARRAYY: A keyword the FITS Standard doesn''t define.' - id: 'arrayz' type: str size: 80 doc: 'ARRAYZ: A keyword the FITS Standard doesn''t define.' - id: 'gstia0' type: str size: 80 doc: 'GSTIA0: A keyword the FITS Standard doesn''t define.' - id: 'degpdy' type: str size: 80 doc: 'DEGPDY: A keyword the FITS Standard doesn''t define.' - id: 'freq' type: str size: 80 doc: 'FREQ: A keyword the FITS Standard doesn''t define.' - id: 'rdate' type: str size: 80 doc: 'RDATE: A keyword the FITS Standard doesn''t define.' - id: 'polarx' type: str size: 80 doc: 'POLARX: A keyword the FITS Standard doesn''t define.' - id: 'polary' type: str size: 80 doc: 'POLARY: A keyword the FITS Standard doesn''t define.' - id: 'ut1utc' type: str size: 80 doc: 'UT1UTC: A keyword the FITS Standard doesn''t define.' - id: 'iatutc' type: str size: 80 doc: 'IATUTC: A keyword the FITS Standard doesn''t define.' - id: 'arrnam' type: str size: 80 doc: 'ARRNAM: A keyword the FITS Standard doesn''t define.' - id: 'numorb' type: str size: 80 doc: 'NUMORB: A keyword the FITS Standard doesn''t define.' - id: 'nopcal' type: str size: 80 doc: 'NOPCAL: A keyword the FITS Standard doesn''t define.' - id: 'end' type: str size: 80 doc: 'END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header.' doc-ref: 'http://ontology.oais.info/fits/keyword/END' - id: 'fill' size: 880 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 28 rows of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns, 78 bytes (NAXIS1).' seq: - id: 'anname' type: str size: 8 doc: 'ANNAME: Column 1 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM1 = ''8A'', 8 characters. Type (heading) of field 1.' - id: 'stabxyz' type: f8 repeat: expr repeat-expr: 3 doc: 'STABXYZ (METERS): Column 2 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM2 = ''3D'', 3 of double-precision floating point. Type (heading) of field 2.' - id: 'nosta' type: s4 doc: 'NOSTA: Column 4 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM4 = ''1J'', a 32-bit integer. Type (heading) of field 4.' - id: 'mntsta' type: s4 doc: 'MNTSTA: Column 5 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM5 = ''1J'', a 32-bit integer. Type (heading) of field 5.' - id: 'staxof' type: f4 doc: 'STAXOF (METERS): Column 6 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM6 = ''1E'', a single-precision floating point. Type (heading) of field 6.' - id: 'poltya' type: str size: 1 doc: 'POLTYA: Column 7 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM7 = ''1A'', 1 character. Type (heading) of field 7.' - id: 'polaa' type: f4 doc: 'POLAA (DEGREES): Column 8 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM8 = ''1E'', a single-precision floating point. Type (heading) of field 8.' - id: 'polcala' type: f4 repeat: expr repeat-expr: 3 doc: 'POLCALA: Column 9 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM9 = ''3E'', 3 of single-precision floating point. Type (heading) of field 9.' - id: 'poltyb' type: str size: 1 doc: 'POLTYB: Column 10 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM10 = ''1A'', 1 character. Type (heading) of field 10.' - id: 'polab' type: f4 doc: 'POLAB (DEGREES): Column 11 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM11 = ''1E'', a single-precision floating point. Type (heading) of field 11.' - id: 'polcalb' type: f4 repeat: expr repeat-expr: 3 doc: 'POLCALB: Column 12 of HDU 2, a binary table (EXTNAME ''AIPS AN'') of 28 rows of 12 columns: TFORM12 = ''3E'', 3 of single-precision floating point. Type (heading) of field 12.'

Linked from