Output Product: HEALPix Information Maps

$SetSchemaPath le3/id/vmpz/out/euc-le3-id-vmpz-HealpixInfoMap.xsd

Data Product Name

$PrintDataProductName

Data Product Custodian

$PrintDataProductCustodian

Name of the Schema File

$PrintSchemaFilename

Last Edited for DPDD Version

1.1

Processing Elements Creating / Updating / Using the Product

Creators:

  • VMPZ_Main (LE3_VMPZ_ID_Main)

Consumers:

  • VMPZ_Visibility (LE3_VMPZ_ID_Visibility)

Processing function using the data product

  • 2PCF-WL, PK-WL, 2PCF-GC, 3PCF-GC, PK-GC, DET-CL, PROF-CL, VMSP-ID

  • SWG-GC, SWG-WL, SWG-CL

Proposed for inclusion in EAS/SAS

This product is proposed for inclusion in SAS: yes

This product is used by different PFs in OU-LE3 and expected to be used in scientific analysis in SWG-GC, SWG-WL and SWG-CL.

Data Product Elements

$PrintDataProductElements

Detailed Description of the Data Product

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

Processing Element(s) creating/using the data product

This output product is composed of InfoMapHealpix, a container with a FITS file in partial HEALPix format (of type le3.id.vmpz.healpixinfomap) 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 InfoMapHealpixParams 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:

$PrintPrimaryHeader fit/euc-le3-id.xml le3.id.vmpz.healpixinfomap

  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 HEALPix Footprint Table (First Extension, Binary Table)

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

$PrintHDUTableContents fit/euc-le3-id.xml le3.id.vmpz.healpixinfomap INFO_MAP

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

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

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

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

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

  6. ORDERING (= ‘RING’ or ‘NESTED’) [StringKeyword]

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

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

  9. NSIDE [IntegerKeyword]

  10. INDEXSCHM (= ‘EXPLICIT’) [StringKeyword]

  11. OBJECT (= ‘PARTIAL’) [StringKeyword]

The table is then expected to contain the following columns:

  1. PIXEL: 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]