Output Product: HEALPix Coverage Mask

Data Product Name

DpdHealpixCoverageVMPZ

Data Product Custodian

IDVMPZ

Name of the Schema File

euc-le3-id-vmpz-HealpixCoverageMask.xsd

Last Edited for DPDD Version

2.0

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:coverageMaskHealpixVMPZ

QualityFlags:

object of type dqc:sqfPlaceHolder

Parameters:

object of type ppr:genericKeyValueParameters

Detailed Description of the Data Product

This output product is between 0 and 1. It is essentially obtained from the combination of the footprint with extra excluded regions corresponding to regions flagged in the bit mask and RMS image collected in MER MERMosaic.

It includes the CoverageMaskHealpix metadata, a container with a FITS file (of type le3.id.vmpz.healpixcoveragemask) describing the coverage mask 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 CoverageMaskHealpixParams 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:

HDU PRIMARY: header

Name

Description

Value

Keywords

SIMPLE

logical

BITPIX

integer

NAXIS

integer

EXTEND

logical

DATE-OBS

e.g. Start date for observations considered

string

DATE-END

e.g. End date for observations considered

string

TELESCOP

e.g. Euclid or -1

string

INSTRUME

e.g. VIS or -1

string

FILTER

e.g. VIS or -1

string

FILTLST

index for combination of filters if intersection of footprints

string

TILEID

e.g. 5237, or -1 if not single tile

integer

LISTID

Product ID for a MER list of tiles

string

NSIDE_WK

Nside used for mosaic frame to HEALPix

string

BITSEL

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

string

SOFTNAME

string

SOFTVERS

string

SOFTINST

string

With time format ‘yyyy-mm-ddThh:mm:ss.sss’ and basic software parameters:

  • SOFTNAME: name of software used [StringKeyword]

  • SOFTVERS: version of software used [StringKeyword]

  • SOFTINST: institute developing the software [StringKeyword]

Partial HEALPix Footprint Table (First Extension, Binary Table)

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

HDU COVERAGE_MASK: header

Name

Description

Value

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

TTYPE3

string

TFORM3

string

PIXTYPE

string

ORDERING

string

COORDSYS

string

EXTNAME

string

NSIDE

integer

INDXSCHM

string

HDU COVERAGE_MASK: 3 columns table

Name

Description

Unit

Format

Columns

PIXEL

Index of the HEALPix pixel cell

NA

FITS K

WEIGHT

Mask value, ranging from O to 1

NA

FITS E

ERROR

Mask error value

NA

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 (= ‘COVERAGE_MASK’) [StringKeyword]

  9. NSIDE [IntegerKeyword]

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

The table is then expected to contain the following columns:

  • PIXEL: index of pixel [K, int64]

  • WEIGHT: weight associated to pixel in [0,1] indicating the fraction of the

pixel actually covered by the footprint (1: not observed/flagged regions) [E, float32]