Output Product: HEALPix Depth Map

Data Product Name

DpdHealpixDepthMapVMPZ

Data Product Custodian

IDVMPZ

Name of the Schema File

euc-le3-id-vmpz-HealpixDepthMap.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:depthMapHealpixVMPZ

QualityFlags:

object of type dqc:sqfPlaceHolder

Parameters:

object of type ppr:genericKeyValueParameters

Detailed Description of the Data Product

This output product is a partial HEALPix map collecting the depth maps, collected as (floating point) weights in the map.

It includes the DepthMapHealpix metadata, a container with a FITS file (of type le3.id.vmpz.healpixdepthmap) describing the depth map for the survey in (partial) HEALPix format, for a given observed band/instrument (Euclid/EXT), and 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, spatialFootprint). Finally, the mask parameters DepthMapHealpixParams 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

BITSEL

/

e.g. Bit mask selection applied based on MER binary values

DEPTHEST

/

Estimator of depth

SOFTNAME

/

SOFTVERS

/

END

  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. BITSEL: identifier of the bit of combination of bits used in the depth map (e.g. 0 for least significant bit,..,18) [StringKeyword]

  11. DEPTHEST: estimator used for depth computation [StringKeyword]

and basic software parameters:

  1. SOFTNAME: name of software used [StringKeyword]

  2. 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 DEPTH_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

WEIGHT

Depth

FITS E

  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 (= ‘DEPTH_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 depth [E, float32]