FITS file EUVEngc4151imgx.fits: Kaitai Struct description

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

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 EUVEngc4151imgx.fits" as a Kaitai Struct description.
formatRegistryIdentifier PRONOM x-fmt/383
label FITS file EUVEngc4151imgx.fits: Kaitai Struct description
specificationLanguage Kaitai Struct
specificationText meta: id: 'fits_file_euvengc4151imgx_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): 9 HDUs. hdu1: HDU 1, the primary HDU, with no data hdu2: HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array hdu3: HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array hdu4: HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array hdu5: HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array hdu6: HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns hdu7: HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns hdu8: HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns hdu9: HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 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, with no data: The header of HDU 1, the primary HDU, with no data: 63 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu2_header' type: 'hdu2_header' doc: 'Header of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array: The header of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array: 73 keyword records of 80 ASCII characters, the last END, in 3 blocks.' - id: 'hdu2_image' type: 'hdu2_image' repeat: expr repeat-expr: 512 doc: 'Image row: One row of the 512 x 512 array of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array: 512 pixels along axis 1.' - id: 'hdu2_fill' size: 2752 doc: 'Fill: Fill after the data of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array, to a whole number of 2880-byte blocks.' - id: 'hdu3_header' type: 'hdu3_header' doc: 'Header of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array: The header of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array: 79 keyword records of 80 ASCII characters, the last END, in 3 blocks.' - id: 'hdu3_image' type: 'hdu3_image' repeat: expr repeat-expr: 300 doc: 'Image row: One row of the 2048 x 300 array of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array: 2048 pixels along axis 1.' - id: 'hdu3_fill' size: 960 doc: 'Fill: Fill after the data of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array, to a whole number of 2880-byte blocks.' - id: 'hdu4_header' type: 'hdu4_header' doc: 'Header of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array: The header of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array: 79 keyword records of 80 ASCII characters, the last END, in 3 blocks.' - id: 'hdu4_image' type: 'hdu4_image' repeat: expr repeat-expr: 300 doc: 'Image row: One row of the 2048 x 300 array of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array: 2048 pixels along axis 1.' - id: 'hdu4_fill' size: 960 doc: 'Fill: Fill after the data of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array, to a whole number of 2880-byte blocks.' - id: 'hdu5_header' type: 'hdu5_header' doc: 'Header of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array: The header of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array: 79 keyword records of 80 ASCII characters, the last END, in 3 blocks.' - id: 'hdu5_image' type: 'hdu5_image' repeat: expr repeat-expr: 300 doc: 'Image row: One row of the 2048 x 300 array of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array: 2048 pixels along axis 1.' - id: 'hdu5_fill' size: 960 doc: 'Fill: Fill after the data of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array, to a whole number of 2880-byte blocks.' - id: 'hdu6_header' type: 'hdu6_header' doc: 'Header of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: The header of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu6_row' type: 'hdu6_row' repeat: expr repeat-expr: 3 doc: 'Table row: One of the 3 rows of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns, 16 bytes (NAXIS1).' - id: 'hdu6_fill' size: 2832 doc: 'Fill: Fill after the data of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns, to a whole number of 2880-byte blocks.' - id: 'hdu7_header' type: 'hdu7_header' doc: 'Header of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: The header of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu7_row' type: 'hdu7_row' repeat: expr repeat-expr: 2 doc: 'Table row: One of the 2 rows of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns, 20 bytes (NAXIS1).' - id: 'hdu7_fill' size: 2840 doc: 'Fill: Fill after the data of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns, to a whole number of 2880-byte blocks.' - id: 'hdu8_header' type: 'hdu8_header' doc: 'Header of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: The header of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu8_row' type: 'hdu8_row' repeat: expr repeat-expr: 2 doc: 'Table row: One of the 2 rows of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns, 20 bytes (NAXIS1).' - id: 'hdu8_fill' size: 2840 doc: 'Fill: Fill after the data of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns, to a whole number of 2880-byte blocks.' - id: 'hdu9_header' type: 'hdu9_header' doc: 'Header of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: The header of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: 72 keyword records of 80 ASCII characters, the last END, in 2 blocks.' - id: 'hdu9_row' type: 'hdu9_row' repeat: expr repeat-expr: 2 doc: 'Table row: One of the 2 rows of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns, 20 bytes (NAXIS1).' - id: 'hdu9_fill' size: 2840 doc: 'Fill: Fill after the data of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns, to a whole number of 2880-byte blocks.' types: 'hdu1_header': doc: 'Header of HDU 1, the primary HDU, with no data: The header of HDU 1, the primary HDU, with no data: 63 keyword records of 80 ASCII characters, the last END, in 2 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: "FITS STANDARD"' doc-ref: 'http://ontology.oais.info/fits/keyword/SIMPLE' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "Character information"' 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: "No image data array present"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXIS' - 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: '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 file was written (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE' - 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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_6' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_7' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_8' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_9' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_10' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_11' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_12' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_13' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_14' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_15' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_16' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_17' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_18' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_19' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'end' type: str size: 80 doc: 'END: This keyword has no associated value. Bytes 9 through 80 shall be filled with ASCII spaces (decimal 32 or hexadecimal 20). The END keyword marks the logical end of the header and must occur in the last 2880-byte FITS block of the header.' doc-ref: 'http://ontology.oais.info/fits/keyword/END' - id: 'fill' size: 720 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu2_header': doc: 'Header of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array: The header of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array: 73 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: "IMAGE 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: "number of bits per data pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/BITPIX' - id: 'naxis' type: str size: 80 doc: 'NAXIS: The value field shall contain a non-negative integer no greater than 999 representing the number of axes in the associated data array. A value of zero signifies that no data follow the header in the HDU. This record''s comment: "number of data axes"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXIS' - id: 'naxis1' type: str size: 80 doc: 'NAXIS1: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record''s comment: "length of data axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'naxis2' type: str size: 80 doc: 'NAXIS2: The NAXISn keywords must be present for all values n = 1, . . . , NAXIS, in increasing order of n, and for no other values of n. The value field of this indexed keyword shall contain a non-negative integer representing the number of elements along Axis n of a data array. This record''s comment: "length of data axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: '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: "required keyword; must = 0"' 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: "required keyword; must = 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of image"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'bscale' type: str size: 80 doc: 'BSCALE: This keyword shall be used, along with the BZERO keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. This record''s comment: "Scale factor for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BSCALE' - id: 'bzero' type: str size: 80 doc: 'BZERO: This keyword shall be used, along with the BSCALE keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. The value field shall contain a floating-point number representing the physical value corresponding to an array value of zero. The default value for this keyword is 0.0. This record''s comment: "Offset for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - id: 'ctype1' type: str size: 80 doc: 'CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "RA in tangent plane projection"' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'crval1' type: str size: 80 doc: 'CRVAL1: World-coordinate value at the reference point of Axis i. This record''s comment: "RA at reference pixel"' 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, . . .). This record''s comment: "reference pixel, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'cdelt1' type: str size: 80 doc: 'CDELT1: Increment of the world coordinate at the reference point for Axis i. The value must not be zero. This record''s comment: "scale, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit1' type: str size: 80 doc: 'CUNIT1: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL1, CDELT1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'ctype2' type: str size: 80 doc: 'CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "DEC in tangent plane projection"' 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. This record''s comment: "DEC at reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'crpix2' type: str size: 80 doc: 'CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record''s comment: "reference pixel, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - 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. This record''s comment: "scale, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit2' type: str size: 80 doc: 'CUNIT2: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL2, CDELT2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'exptime' type: str size: 80 doc: 'EXPTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Primbsch/deadtime corrected exposure time"' - id: 'rawexp' type: str size: 80 doc: 'RAWEXP: A keyword the FITS Standard doesn''t define. This record''s comment: "Uncorrected exposure time"' - id: 'filename' type: str size: 80 doc: 'FILENAME: A keyword the FITS Standard doesn''t define.' - 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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Deep Survey"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'tierrabs' type: str size: 80 doc: 'TIERRABS: A keyword the FITS Standard doesn''t define. This record''s comment: "Timing precision (seconds)"' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_6' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_7' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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: 2800 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu2_image': doc: 'Image row: One row of the 512 x 512 array of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array: 512 pixels along axis 1.' seq: - id: 'pixel' type: s2 repeat: expr repeat-expr: 512 doc: 'Pixel value: The values of the 512 x 512 array of HDU 2, an image extension (EXTNAME ''ds''), a 512 x 512 array, 16-bit two''s complement integers (BITPIX = 16), one row of 512 values per "hdu2_image" record. Axis 1: RA---TAN (deg). Axis 2: DEC--TAN (deg). Physical value = BZERO + BSCALE x stored value. Physical value = raw * 1.0 + 0.0.' 'hdu3_header': doc: 'Header of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array: The header of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array: 79 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: "IMAGE extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional image"' 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 image columns"' 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 image rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' 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: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of image"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'bscale' type: str size: 80 doc: 'BSCALE: This keyword shall be used, along with the BZERO keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. This record''s comment: "Scale factor for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BSCALE' - id: 'bzero' type: str size: 80 doc: 'BZERO: This keyword shall be used, along with the BSCALE keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. The value field shall contain a floating-point number representing the physical value corresponding to an array value of zero. The default value for this keyword is 0.0. This record''s comment: "Offset for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - id: 'ctype1' type: str size: 80 doc: 'CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "Wavelength"' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'crval1' type: str size: 80 doc: 'CRVAL1: World-coordinate value at the reference point of Axis i. This record''s comment: "Wavelength at reference pixel"' 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, . . .). This record''s comment: "reference pixel, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'cdelt1' type: str size: 80 doc: 'CDELT1: Increment of the world coordinate at the reference point for Axis i. The value must not be zero. This record''s comment: "scale, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit1' type: str size: 80 doc: 'CUNIT1: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL1, CDELT1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'ctype2' type: str size: 80 doc: 'CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "Imaging angle"' 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. This record''s comment: "Imaging angle at reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'crpix2' type: str size: 80 doc: 'CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record''s comment: "reference pixel, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - 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. This record''s comment: "scale, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit2' type: str size: 80 doc: 'CUNIT2: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL2, CDELT2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'exptime' type: str size: 80 doc: 'EXPTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Primbsch/deadtime corrected exposure time"' - id: 'rawexp' type: str size: 80 doc: 'RAWEXP: A keyword the FITS Standard doesn''t define. This record''s comment: "Uncorrected exposure time"' - id: 'filename' type: str size: 80 doc: 'FILENAME: A keyword the FITS Standard doesn''t define.' - 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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Short Wavelength Spectrometer"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'detstrip' type: str size: 80 doc: 'DETSTRIP: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector strip"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'tierrabs' type: str size: 80 doc: 'TIERRABS: A keyword the FITS Standard doesn''t define. This record''s comment: "Timing precision (seconds)"' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_6' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_7' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_8' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_9' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_10' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_11' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_12' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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: 2320 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu3_image': doc: 'Image row: One row of the 2048 x 300 array of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array: 2048 pixels along axis 1.' seq: - id: 'pixel' type: s2 repeat: expr repeat-expr: 2048 doc: 'Pixel value: The values of the 2048 x 300 array of HDU 3, an image extension (EXTNAME ''sw_night''), a 2048 x 300 array, 16-bit two''s complement integers (BITPIX = 16), one row of 2048 values per "hdu3_image" record. Axis 1: WAVELENGTH (angstrom). Axis 2: ANGLE (deg). Physical value = BZERO + BSCALE x stored value. Physical value = raw * 1.0 + 0.0.' 'hdu4_header': doc: 'Header of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array: The header of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array: 79 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: "IMAGE extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional image"' 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 image columns"' 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 image rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' 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: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of image"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'bscale' type: str size: 80 doc: 'BSCALE: This keyword shall be used, along with the BZERO keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. This record''s comment: "Scale factor for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BSCALE' - id: 'bzero' type: str size: 80 doc: 'BZERO: This keyword shall be used, along with the BSCALE keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. The value field shall contain a floating-point number representing the physical value corresponding to an array value of zero. The default value for this keyword is 0.0. This record''s comment: "Offset for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - id: 'ctype1' type: str size: 80 doc: 'CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "Wavelength"' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'crval1' type: str size: 80 doc: 'CRVAL1: World-coordinate value at the reference point of Axis i. This record''s comment: "Wavelength at reference pixel"' 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, . . .). This record''s comment: "reference pixel, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'cdelt1' type: str size: 80 doc: 'CDELT1: Increment of the world coordinate at the reference point for Axis i. The value must not be zero. This record''s comment: "scale, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit1' type: str size: 80 doc: 'CUNIT1: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL1, CDELT1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'ctype2' type: str size: 80 doc: 'CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "Imaging angle"' 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. This record''s comment: "Imaging angle at reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'crpix2' type: str size: 80 doc: 'CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record''s comment: "reference pixel, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - 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. This record''s comment: "scale, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit2' type: str size: 80 doc: 'CUNIT2: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL2, CDELT2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'exptime' type: str size: 80 doc: 'EXPTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Primbsch/deadtime corrected exposure time"' - id: 'rawexp' type: str size: 80 doc: 'RAWEXP: A keyword the FITS Standard doesn''t define. This record''s comment: "Uncorrected exposure time"' - id: 'filename' type: str size: 80 doc: 'FILENAME: A keyword the FITS Standard doesn''t define.' - 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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Medium Wavelength Spectrometer"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'detstrip' type: str size: 80 doc: 'DETSTRIP: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector strip"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'tierrabs' type: str size: 80 doc: 'TIERRABS: A keyword the FITS Standard doesn''t define. This record''s comment: "Timing precision (seconds)"' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_6' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_7' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_8' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_9' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_10' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_11' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_12' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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: 2320 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu4_image': doc: 'Image row: One row of the 2048 x 300 array of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array: 2048 pixels along axis 1.' seq: - id: 'pixel' type: s2 repeat: expr repeat-expr: 2048 doc: 'Pixel value: The values of the 2048 x 300 array of HDU 4, an image extension (EXTNAME ''mw''), a 2048 x 300 array, 16-bit two''s complement integers (BITPIX = 16), one row of 2048 values per "hdu4_image" record. Axis 1: WAVELENGTH (angstrom). Axis 2: ANGLE (deg). Physical value = BZERO + BSCALE x stored value. Physical value = raw * 1.0 + 0.0.' 'hdu5_header': doc: 'Header of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array: The header of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array: 79 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: "IMAGE extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional image"' 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 image columns"' 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 image rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' 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: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of image"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'bscale' type: str size: 80 doc: 'BSCALE: This keyword shall be used, along with the BZERO keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. This record''s comment: "Scale factor for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BSCALE' - id: 'bzero' type: str size: 80 doc: 'BZERO: This keyword shall be used, along with the BSCALE keyword, to linearly scale the array pixel values (i.e., the actual values stored in the FITS file) to transform them into the physical values that they represent using Eq. 3. The value field shall contain a floating-point number representing the physical value corresponding to an array value of zero. The default value for this keyword is 0.0. This record''s comment: "Offset for pixel values"' doc-ref: 'http://ontology.oais.info/fits/keyword/BZERO' - id: 'ctype1' type: str size: 80 doc: 'CTYPE1: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "Wavelength"' doc-ref: 'http://ontology.oais.info/fits/keyword/CTYPEi' - id: 'crval1' type: str size: 80 doc: 'CRVAL1: World-coordinate value at the reference point of Axis i. This record''s comment: "Wavelength at reference pixel"' 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, . . .). This record''s comment: "reference pixel, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - id: 'cdelt1' type: str size: 80 doc: 'CDELT1: Increment of the world coordinate at the reference point for Axis i. The value must not be zero. This record''s comment: "scale, axis 1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit1' type: str size: 80 doc: 'CUNIT1: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL1, CDELT1"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'ctype2' type: str size: 80 doc: 'CTYPE2: Type for the Intermediate-coordinate Axis i. Any coordinate type that is not covered by this Standard or an officially recognized FITS convention shall be taken to be linear. This record''s comment: "Imaging angle"' 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. This record''s comment: "Imaging angle at reference pixel"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRVALi' - id: 'crpix2' type: str size: 80 doc: 'CRPIX2: Location of the reference point in the image for Axis j corresponding to r j in Eq. (9). Note that the reference point may lie outside the image and that the first pixel in the image has pixel coordinates (1.0, 1.0, . . .). This record''s comment: "reference pixel, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CRPIXj' - 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. This record''s comment: "scale, axis 2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CDELTi' - id: 'cunit2' type: str size: 80 doc: 'CUNIT2: Physical units of CRVAL and CDELT for Axis i. Note that units should always be specified (see Sect. 4.3). Units for celestial coordinate systems defined in this Standard must be degrees. This record''s comment: "units of CRVAL2, CDELT2"' doc-ref: 'http://ontology.oais.info/fits/keyword/CUNITi' - id: 'exptime' type: str size: 80 doc: 'EXPTIME: A keyword the FITS Standard doesn''t define. This record''s comment: "Primbsch/deadtime corrected exposure time"' - id: 'rawexp' type: str size: 80 doc: 'RAWEXP: A keyword the FITS Standard doesn''t define. This record''s comment: "Uncorrected exposure time"' - id: 'filename' type: str size: 80 doc: 'FILENAME: A keyword the FITS Standard doesn''t define.' - 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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Long Wavelength Spectrometer"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'detstrip' type: str size: 80 doc: 'DETSTRIP: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector strip"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'tierrabs' type: str size: 80 doc: 'TIERRABS: A keyword the FITS Standard doesn''t define. This record''s comment: "Timing precision (seconds)"' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_6' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_7' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_8' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_9' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_10' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_11' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_12' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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: 2320 doc: 'Fill: Blank records after END, filling the header to a whole number of 2880-byte blocks.' 'hdu5_image': doc: 'Image row: One row of the 2048 x 300 array of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array: 2048 pixels along axis 1.' seq: - id: 'pixel' type: s2 repeat: expr repeat-expr: 2048 doc: 'Pixel value: The values of the 2048 x 300 array of HDU 5, an image extension (EXTNAME ''lw''), a 2048 x 300 array, 16-bit two''s complement integers (BITPIX = 16), one row of 2048 values per "hdu5_image" record. Axis 1: WAVELENGTH (angstrom). Axis 2: ANGLE (deg). Physical value = BZERO + BSCALE x stored value. Physical value = raw * 1.0 + 0.0.' 'hdu6_header': doc: 'Header of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: The header of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: 72 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: "Binary table extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional binary table"' 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: "The number of rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' doc-ref: 'http://ontology.oais.info/fits/keyword/PCOUNT' - id: 'gcount' type: str size: 80 doc: 'GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record''s comment: "Only one group"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'tfields' type: str size: 80 doc: 'TFIELDS: The value field shall contain a non-negative integer representing the number of fields in each row. The maximum permissible value is 999. This record''s comment: "Number of fields per row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - id: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of table"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'blank' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype1' type: str size: 80 doc: 'TTYPE1: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Name of limited value"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform1' type: str size: 80 doc: 'TFORM1: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit1' type: str size: 80 doc: 'TUNIT1: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp1' type: str size: 80 doc: 'TDISP1: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_2' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype2' type: str size: 80 doc: 'TTYPE2: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Lower limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform2' type: str size: 80 doc: 'TFORM2: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit2' type: str size: 80 doc: 'TUNIT2: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp2' type: str size: 80 doc: 'TDISP2: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_3' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype3' type: str size: 80 doc: 'TTYPE3: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Upper limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform3' type: str size: 80 doc: 'TFORM3: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit3' type: str size: 80 doc: 'TUNIT3: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp3' type: str size: 80 doc: 'TDISP3: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_4' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: '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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Deep Survey"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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' 'hdu6_row': doc: 'Table row: One of the 3 rows of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns, 16 bytes (NAXIS1).' seq: - id: 'name' type: str size: 8 doc: 'NAME: Column 1 of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: TFORM1 = ''8A'', 8 characters. Name of limited value.' - id: 'low' type: f4 doc: 'LOW (UNKNOWN): Column 2 of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: TFORM2 = ''1E'', a single-precision floating point. Lower limit.' - id: 'high' type: f4 doc: 'HIGH (UNKNOWN): Column 3 of HDU 6, a binary table (EXTNAME ''ds_limits'') of 3 rows of 3 columns: TFORM3 = ''1E'', a single-precision floating point. Upper limit.' 'hdu7_header': doc: 'Header of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: The header of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: 72 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: "Binary table extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional binary table"' 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: "The number of rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' doc-ref: 'http://ontology.oais.info/fits/keyword/PCOUNT' - id: 'gcount' type: str size: 80 doc: 'GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record''s comment: "Only one group"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'tfields' type: str size: 80 doc: 'TFIELDS: The value field shall contain a non-negative integer representing the number of fields in each row. The maximum permissible value is 999. This record''s comment: "Number of fields per row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - id: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of table"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'blank' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype1' type: str size: 80 doc: 'TTYPE1: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Name of limited value"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform1' type: str size: 80 doc: 'TFORM1: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit1' type: str size: 80 doc: 'TUNIT1: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp1' type: str size: 80 doc: 'TDISP1: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_2' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype2' type: str size: 80 doc: 'TTYPE2: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Lower limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform2' type: str size: 80 doc: 'TFORM2: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit2' type: str size: 80 doc: 'TUNIT2: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp2' type: str size: 80 doc: 'TDISP2: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_3' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype3' type: str size: 80 doc: 'TTYPE3: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Upper limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform3' type: str size: 80 doc: 'TFORM3: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit3' type: str size: 80 doc: 'TUNIT3: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp3' type: str size: 80 doc: 'TDISP3: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_4' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: '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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Short Wavelength Spectrometer"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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' 'hdu7_row': doc: 'Table row: One of the 2 rows of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns, 20 bytes (NAXIS1).' seq: - id: 'name' type: str size: 12 doc: 'NAME: Column 1 of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: TFORM1 = ''12A'', 12 characters. Name of limited value.' - id: 'low' type: f4 doc: 'LOW (UNKNOWN): Column 2 of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: TFORM2 = ''1E'', a single-precision floating point. Lower limit.' - id: 'high' type: f4 doc: 'HIGH (UNKNOWN): Column 3 of HDU 7, a binary table (EXTNAME ''sw_night_limits'') of 2 rows of 3 columns: TFORM3 = ''1E'', a single-precision floating point. Upper limit.' 'hdu8_header': doc: 'Header of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: The header of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: 72 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: "Binary table extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional binary table"' 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: "The number of rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' doc-ref: 'http://ontology.oais.info/fits/keyword/PCOUNT' - id: 'gcount' type: str size: 80 doc: 'GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record''s comment: "Only one group"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'tfields' type: str size: 80 doc: 'TFIELDS: The value field shall contain a non-negative integer representing the number of fields in each row. The maximum permissible value is 999. This record''s comment: "Number of fields per row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - id: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of table"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'blank' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype1' type: str size: 80 doc: 'TTYPE1: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Name of limited value"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform1' type: str size: 80 doc: 'TFORM1: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit1' type: str size: 80 doc: 'TUNIT1: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp1' type: str size: 80 doc: 'TDISP1: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_2' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype2' type: str size: 80 doc: 'TTYPE2: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Lower limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform2' type: str size: 80 doc: 'TFORM2: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit2' type: str size: 80 doc: 'TUNIT2: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp2' type: str size: 80 doc: 'TDISP2: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_3' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype3' type: str size: 80 doc: 'TTYPE3: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Upper limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform3' type: str size: 80 doc: 'TFORM3: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit3' type: str size: 80 doc: 'TUNIT3: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp3' type: str size: 80 doc: 'TDISP3: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_4' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: '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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Medium Wavelength Spectrometer"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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' 'hdu8_row': doc: 'Table row: One of the 2 rows of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns, 20 bytes (NAXIS1).' seq: - id: 'name' type: str size: 12 doc: 'NAME: Column 1 of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: TFORM1 = ''12A'', 12 characters. Name of limited value.' - id: 'low' type: f4 doc: 'LOW (UNKNOWN): Column 2 of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: TFORM2 = ''1E'', a single-precision floating point. Lower limit.' - id: 'high' type: f4 doc: 'HIGH (UNKNOWN): Column 3 of HDU 8, a binary table (EXTNAME ''mw_limits'') of 2 rows of 3 columns: TFORM3 = ''1E'', a single-precision floating point. Upper limit.' 'hdu9_header': doc: 'Header of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: The header of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: 72 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: "Binary table extension"' doc-ref: 'http://ontology.oais.info/fits/keyword/XTENSION' - id: 'bitpix' type: str size: 80 doc: 'BITPIX: The value field shall contain an integer. The absolute value is used in computing the sizes of data structures. It shall specify the number of bits that represent a data value in the associated data array. The only valid values of BITPIX are 8 (character or unsigned binary integer), 16, 32 and 64 (two''s complement binary integers of that many bits), -32 (IEEE single-precision floating point) and -64 (IEEE double-precision floating point). This record''s comment: "8-bit bytes"' 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: "2-dimensional binary table"' 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: "The number of rows"' doc-ref: 'http://ontology.oais.info/fits/keyword/NAXISn' - id: 'pcount' type: str size: 80 doc: 'PCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. In IMAGE (Sect. 7.1) and TABLE (Sect. 7.2) extensions this keyword must have the value 0; in BINTABLE extensions (Sect. 7.3) it is used to specify the number of bytes that follow the main data table in the supplemental data area called the heap. This record''s comment: "Size of special data area"' doc-ref: 'http://ontology.oais.info/fits/keyword/PCOUNT' - id: 'gcount' type: str size: 80 doc: 'GCOUNT: The value field shall contain an integer that shall be used in any way appropriate to define the data structure, consistent with Eq. 2. This keyword must have the value 1 in the IMAGE, TABLE, and BINTABLE standard extensions defined in Sect. 7. This keyword is also used in the random-groups structure (Sect. 6) to specify the number of random groups present. This record''s comment: "Only one group"' doc-ref: 'http://ontology.oais.info/fits/keyword/GCOUNT' - id: 'tfields' type: str size: 80 doc: 'TFIELDS: The value field shall contain a non-negative integer representing the number of fields in each row. The maximum permissible value is 999. This record''s comment: "Number of fields per row"' doc-ref: 'http://ontology.oais.info/fits/keyword/TFIELDS' - id: 'extname' type: str size: 80 doc: 'EXTNAME: The value field shall contain a character string to be used to distinguish among different extensions of the same type, i.e., with the same value of XTENSION, in a FITS file. Within this context, the primary array should be considered as equivalent to an IMAGE extension. This record''s comment: "Name of table"' doc-ref: 'http://ontology.oais.info/fits/keyword/EXTNAME' - id: 'blank' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype1' type: str size: 80 doc: 'TTYPE1: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Name of limited value"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform1' type: str size: 80 doc: 'TFORM1: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit1' type: str size: 80 doc: 'TUNIT1: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp1' type: str size: 80 doc: 'TDISP1: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%s"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_2' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype2' type: str size: 80 doc: 'TTYPE2: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Lower limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform2' type: str size: 80 doc: 'TFORM2: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit2' type: str size: 80 doc: 'TUNIT2: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp2' type: str size: 80 doc: 'TDISP2: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_3' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: 'ttype3' type: str size: 80 doc: 'TTYPE3: The value field for this indexed keyword shall contain a character string giving the name of Field n. It is strongly recommended that every field of the table be assigned a unique, case-insensitive name with this keyword, and it is recommended that the character string be composed only of upper- and lower-case letters, digits, and the underscore ('' '', decimal 95, hexadecimal 5F) character. This record''s comment: "Upper limit"' doc-ref: 'http://ontology.oais.info/fits/keyword/TTYPEn' - id: 'tform3' type: str size: 80 doc: 'TFORM3: The TFORMn keywords must be present for all values n = 1, . . . , TFIELDS and for no other values of n. The value field of this indexed keyword shall contain a character string describing the format in which Field n is encoded. Only the formats in Table 15, interpreted as Fortran (ISO 2004) input formats and discussed in more detail in Sect. 7.2.5, are permitted for encoding.' doc-ref: 'http://ontology.oais.info/fits/keyword/TFORMn' - id: 'tunit3' type: str size: 80 doc: 'TUNIT3: The value field shall contain a character string describing the physical units in which the quantity in Field n, after any application of TSCALn and TZEROn, is expressed. Units must follow the prescriptions in Sect. 4.3.' doc-ref: 'http://ontology.oais.info/fits/keyword/TUNITn' - id: 'tdisp3' type: str size: 80 doc: 'TDISP3: The value field of this indexed keyword shall contain a character string describing the format recommended for displaying an ASCII-text representation of of the contents of Field n. This keyword overrides the default display format given by the TFORMn keyword. If the table value has been scaled, the physical value, derived using Eq. 7, shall be displayed. This record''s comment: "%15.7g"' doc-ref: 'http://ontology.oais.info/fits/keyword/TDISPn' - id: 'blank_4' type: str size: 80 doc: '(blank): A keyword record whose keyword field is all spaces: commentary text in Bytes 9 through 80. Blank records just before END may be non-significant fill.' doc-ref: 'http://ontology.oais.info/fits/keyword/blank' - id: '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: "EUVE Science Archive"' doc-ref: 'http://ontology.oais.info/fits/keyword/ORIGIN' - id: 'creator' type: str size: 80 doc: 'CREATOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Fitsio version 11-May-1995"' - id: 'telescop' type: str size: 80 doc: 'TELESCOP: The value field shall contain a character string identifying the telescope used to acquire the data associated with the header. This record''s comment: "Extreme Ultraviolet Explorer"' doc-ref: 'http://ontology.oais.info/fits/keyword/TELESCOP' - id: 'insttype' type: str size: 80 doc: 'INSTTYPE: A keyword the FITS Standard doesn''t define. This record''s comment: "Instrument type (DS/S, SCANNER)"' - 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: "Deep Survey - Spectrometer"' doc-ref: 'http://ontology.oais.info/fits/keyword/INSTRUME' - id: 'detnam' type: str size: 80 doc: 'DETNAM: A keyword the FITS Standard doesn''t define. This record''s comment: "Long Wavelength Spectrometer"' - id: 'object' type: str size: 80 doc: 'OBJECT: The value field shall contain a character string giving a name for the object observed. This record''s comment: "Name of observed object"' doc-ref: 'http://ontology.oais.info/fits/keyword/OBJECT' - id: 'ra_obj' type: str size: 80 doc: 'RA_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the object (degrees)"' - id: 'dec_obj' type: str size: 80 doc: 'DEC_OBJ: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the object (degrees)"' - id: 'ra_pnt' type: str size: 80 doc: 'RA_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. of the pointing direction (degrees)"' - id: 'dec_pnt' type: str size: 80 doc: 'DEC_PNT: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination of the pointing direction (degrees)"' - id: 'ra_proc' type: str size: 80 doc: 'RA_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "R.A. used to process data (degrees)"' - id: 'dec_proc' type: str size: 80 doc: 'DEC_PROC: A keyword the FITS Standard doesn''t define. This record''s comment: "Declination used to process data (degrees)"' - 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. This record''s comment: "Original observing P.I. (EUVE = calibration)"' 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. This record''s comment: "Start date of observation (dd/mm/yy) 19yy"' 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: "Start time of observation (hh:mm:ss GMT)"' - id: 'date_end' type: str size: 80 doc: 'DATE-END: The value field of this keyword shall contain a character string in ISO-8601 format that specifies the stop time of data acquisition in the time system specified by the TIMESYS keyword. This record''s comment: "End date of observation (dd/mm/yy) 19yy"' doc-ref: 'http://ontology.oais.info/fits/keyword/DATE-END' - id: 'time_end' type: str size: 80 doc: 'TIME-END: A keyword the FITS Standard doesn''t define. This record''s comment: "End time of observation (hh:mm:ss GMT)"' - id: 'obs_mode' type: str size: 80 doc: 'OBS_MODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Inertial pointing mode"' - id: 'dither' type: str size: 80 doc: 'DITHER: A keyword the FITS Standard doesn''t define. This record''s comment: "Spacecraft dither type (DITHERED, SPIRAL, NONE)"' - id: 'detmode' type: str size: 80 doc: 'DETMODE: A keyword the FITS Standard doesn''t define. This record''s comment: "Detector position conversion mode (WSZ or XY)"' - id: 'off_axis' type: str size: 80 doc: 'OFF-AXIS: A keyword the FITS Standard doesn''t define. This record''s comment: "Was this pointing done off-axis"' - id: 'moving' type: str size: 80 doc: 'MOVING: A keyword the FITS Standard doesn''t define. This record''s comment: "Did the source position vary during observation"' - id: 'daynight' type: str size: 80 doc: 'DAYNIGHT: A keyword the FITS Standard doesn''t define. This record''s comment: "Day/night data indicator (DAY, NIGHT, BOTH)"' - id: 'validtim' type: str size: 80 doc: 'VALIDTIM: A keyword the FITS Standard doesn''t define. This record''s comment: "Amount of telemetry present (seconds)"' - id: 'ra_unit' type: str size: 80 doc: 'RA_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Right Ascension"' - id: 'dec_unit' type: str size: 80 doc: 'DEC_UNIT: A keyword the FITS Standard doesn''t define. This record''s comment: "Units for Declination"' - 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: "Coordinate equinox"' doc-ref: 'http://ontology.oais.info/fits/keyword/EQUINOX' - id: 'radecsys' type: str size: 80 doc: 'RADECSYS: A keyword the FITS Standard doesn''t define. This record''s comment: "Frame of reference of coordinates"' - id: 'timesys' type: str size: 80 doc: 'TIMESYS: The value field of this keyword shall contain a character-string code for the time scale of the time-related keywords. The recommended values for this keyword in Table 30 have well-defined meanings, but other values may be used. If this keyword is absent, ''UTC'' must be assumed. This record''s comment: "MJD = JD - 2400000.5"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMESYS' - id: 'timezero' type: str size: 80 doc: 'TIMEZERO: A keyword the FITS Standard doesn''t define. This record''s comment: "No time offset required for EUVE event times"' - id: 'timeunit' type: str size: 80 doc: 'TIMEUNIT: The value field of this keyword shall contain a character string that specifies the time unit; the value should be one of those given in Table 34. This time unit shall apply to all time instances and durations that do not have an implied time unit (such as is the case for JD, MJD, ISO-8601, J and B epochs). If this keyword is absent, ''s'' shall be assumed. This record''s comment: "Units for TSTART, TSTOP, TIMEZERO"' doc-ref: 'http://ontology.oais.info/fits/keyword/TIMEUNIT' - id: 'clockcor' type: str size: 80 doc: 'CLOCKCOR: A keyword the FITS Standard doesn''t define. This record''s comment: "Not corrected to UT"' - id: 'timeref' type: str size: 80 doc: 'TIMEREF: A keyword the FITS Standard doesn''t define. This record''s comment: "No corrections applied (barycentric, etc.)"' - id: 'tassign' type: str size: 80 doc: 'TASSIGN: A keyword the FITS Standard doesn''t define. This record''s comment: "Event times are assigned at the satellite"' - id: 'tstart' type: str size: 80 doc: 'TSTART: The value field of this keyword shall contain the value of the start time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of start of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTART' - id: 'tstop' type: str size: 80 doc: 'TSTOP: The value field of this keyword shall contain the value of the stop time of data acquisition in units of TIMEUNIT, relative to MJDREF, JDREF, or DATEREF and TIMEOFFS, in the time system specified by the TIMESYS keyword. This record''s comment: "Time of end of observation (seconds)"' doc-ref: 'http://ontology.oais.info/fits/keyword/TSTOP' - id: 'mjdref' type: str size: 80 doc: 'MJDREF: A keyword the FITS Standard doesn''t define. This record''s comment: "MJD of SC clock start, 24.00 May 1968"' - id: 'egocsver' type: str size: 80 doc: 'EGOCSVER: A keyword the FITS Standard doesn''t define. This record''s comment: "Software version used to produce this data"' - id: 'refvers' type: str size: 80 doc: 'REFVERS: A keyword the FITS Standard doesn''t define. This record''s comment: "Reference calibration dataset version used"' - id: 'inherit' type: str size: 80 doc: 'INHERIT: The value field shall contain a logical value of T or F to indicate whether or not the current extension should inherit the keywords in the primary header of the FITS file. This record''s comment: "Do not inherit cards from the primary header"' doc-ref: 'http://ontology.oais.info/fits/keyword/INHERIT' - id: 'comment' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_2' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_3' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_4' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: 'comment_5' type: str size: 80 doc: 'COMMENT: This keyword may be used to supply any comments regarding the FITS file.' doc-ref: 'http://ontology.oais.info/fits/keyword/COMMENT' - id: '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' 'hdu9_row': doc: 'Table row: One of the 2 rows of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns, 20 bytes (NAXIS1).' seq: - id: 'name' type: str size: 12 doc: 'NAME: Column 1 of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: TFORM1 = ''12A'', 12 characters. Name of limited value.' - id: 'low' type: f4 doc: 'LOW (UNKNOWN): Column 2 of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: TFORM2 = ''1E'', a single-precision floating point. Lower limit.' - id: 'high' type: f4 doc: 'HIGH (UNKNOWN): Column 3 of HDU 9, a binary table (EXTNAME ''lw_limits'') of 2 rows of 3 columns: TFORM3 = ''1E'', a single-precision floating point. Upper limit.'

Linked from