Output Product: MOC Information Maps

Data product name

VMPZIDMOCInfoMap

Data product custodian

VMPZ-ID

Data model tag

(TBF for ML2A)

Name of the Schema file

(TBF for ML2A)

Schema documentation tag

(TBF for ML2A)

Data product elements

(TBF for ML2A)

Processing Element(s) creating/using the data product

VMPZ-ID

Processing function using the data product

LE3

Detailed description of the data product

This output product collects environmental/instrumental information for a filter of an instrument to ultimately compute depth maps.

This output product is composed of InfoMapMOC, a container with a FITS file in MOC HEALPix format (of type le3.id.vmpz.mocinfomap) collecting environmental/instrumental information for a filter of an instrument to ultimately compute depth maps. A raw description with polygons of the envelope of the sky covered is added as well to ease future queries on the product (SpatialCoverage metadata, see spatialFootprint). Finally, the map parameters InfoMapMOCParams can optionally be associated to the product.

Keywords (Primary HDU)

The primary HDU is expected to contain the following keywords, characterizing important parameters of the input product:

  1. DATE-OBS: start of observation with format ‘yyyy-mm-ddThh:mm:ss.sss’ [StringKeyword]

  2. DATE-END: end of observation with format ‘yyyy-mm-ddThh:mm:ss.sss’ [StringKeyword]

  3. TELESCOP: name of the telescope [StringKeyword]

  4. INSTRUME: name of the instrument [StringKeyword]

  5. FILTER: name of the filter [StringKeyword]

  6. FILTLST: selection of filter if intersection of multiple footprints [StringKeyword]

  7. TILEID: identifier of the MER Tile processed (-1 if multiple Tiles) [IntegerKeyword]

  8. LISTID: identifier of a MER list of tiles product (-1 if single Tile) [StringKeyword]

  9. NSIDE_WK: Nside parameter used for frame->HEALPix [StringKeyword]

  10. INFO: Information collected in the maps, e.g. “Noise”, “PSF” [StringKeyword]

  11. STATS: statiscts collected - e.g. RMS, median, max [StringKeyword]

    and basic software parameters:

  12. SOFTNAME: name of software used [StringKeyword]

  13. SOFTVERS: version of software used [StringKeyword]

Partial MOC Footprint Table (First Extension, Binary Table)

The following keywords are used to describe what MOC conventions are followed:

  1. TTYPE1 (= ‘UNIQ’) [StringKeyword]

  2. TFORM1 (= ‘K’) [StringKeyword]

  3. TTYPE2 (= ‘WEIGHT’) [StringKeyword]

  4. TFORM2 (= ‘E’) [StringKeyword]

  5. PIXTYPE (= ‘HEALPIX’) [StringKeyword]

  6. ORDERING (= ‘NUNIQ’) [StringKeyword]

  7. COORDSYS (= ‘C’=celestial, ‘E’=ecliptic or ‘G’=galactic) [StringKeyword]

  8. MOCORDER (best HEALPix order) [IntegerKeyword]

  9. MOCTYPE [StringKeyword]

  10. DATE [StringKeyword]

  11. EXTNAME (= ‘INFO_MAP’) [StringKeyword]

The table is then expected to contain the following columns:

  1. UNIQ: index of pixel [K, int64]

  2. WEIGHT: (floating-point) weight associated to pixel indicating the value of the instrumental or environmental parameter collected [E, float32]