Output Product: HEALPix Information Maps¶

Data Product Name¶

DpdHealpixInfoMapVMPZ

Data Product Custodian¶

IDVMPZ

Name of the Schema File¶

euc-le3-id-vmpz-HealpixInfoMap.xsd

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¶

Header:: object of type sys:genericHeader
Data:: object of type vmpzid:infoMapHealpixVMPZ
QualityFlags:: object of type dqc:sqfPlaceHolder
Parameters:: object of type ppr:genericKeyValueParameters

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:

SIMPLE	/
BITPIX	/
NAXIS	/
EXTEND	/
DATE-OBS	/	e.g. Start date for observations considered
DATE-END	/	e.g. End date for observations considered
TELESCOP	/	e.g. Euclid or -1
INSTRUME	/	e.g. VIS or -1
FILTER	/	e.g. VIS or -1
FILTLST	/	index for combination of filters if intersection of footprints
TILEID	/	e.g. 5237, or -1 if not single tile
LISTID	/	Product ID for a MER list of tiles
NSIDE_WK	/	Nside used for mosaic frame to HEALPix
INFO	/	Info collected e.g. Noise, PSF, Seeing, Airmass, SAA etc
STATS	/	e.g. RMS, median, max, min
SOFTNAME	/
SOFTVERS	/
END

DATE-OBS: start of observation with format ‘yyyy-mm-ddThh:mm:ss.sss’ [StringKeyword]
DATE-END: end of observation with format ‘yyyy-mm-ddThh:mm:ss.sss’ [StringKeyword]
TELESCOP: name of the telescope [StringKeyword]
INSTRUME: name of the instrument [StringKeyword]
FILTER: name of the filter [StringKeyword]
FILTLST: selection of filter if intersection of multiple footprints [StringKeyword]
TILEID: identifier of the MER Tile processed (-1 if multiple Tiles) [IntegerKeyword]
LISTID: identifier of a MER list of tiles product (-1 if single Tile) [StringKeyword]
NSIDE_WK: Nside parameter used for frame->HEALPix [StringKeyword]
INFO: Information collected in the maps, e.g. “Noise”, “PSF” [StringKeyword]
STATS: statiscts collected - e.g. RMS, median, max [StringKeyword]

and basic software parameters:
SOFTNAME: name of software used [StringKeyword]
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:

HDU INFO_MAP
Keywords	XTENSION		string
	BITPIX		integer
	NAXIS		integer
	NAXIS1		integer
	NAXIS2		integer
	PCOUNT		integer
	GCOUNT		integer
	TFIELDS		integer
	TTYPE1		string
	TFORM1		string
	TTYPE2		string
	TFORM2		string
	PIXTYPE		string
	ORDERING		string
	COORDSYS		string
	EXTNAME		string
	NSIDE		integer
	INDXSCHM		string
	OBJECT		string
2 columns table
Columns	PIXEL	Index of the HEALPix pixel cell	FITS K
Columns	WEIGHT	Mask value, ranging from O to 1	FITS E

TTYPE1 (= ‘PIXEL’) [StringKeyword]
TFORM1 (= ‘K’) [StringKeyword]
TTYPE2 (= ‘WEIGHT’) [StringKeyword]
TFORM2 (= ‘E’) [StringKeyword]
PIXTYPE (= ‘HEALPIX’) [StringKeyword]
ORDERING (= ‘RING’ or ‘NESTED’) [StringKeyword]
COORDSYS (= ‘C’=celestial, ‘E’=ecliptic or ‘G’=galactic) [StringKeyword]
EXTNAME (= ‘INFO_MAP’) [StringKeyword]
NSIDE [IntegerKeyword]
INDEXSCHM (= ‘EXPLICIT’) [StringKeyword]
OBJECT (= ‘PARTIAL’) [StringKeyword]

The table is then expected to contain the following columns:

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