Output Product: MOC Visibility Mask

Metadata

Data product name	DpdMOCVisibilityMaskVMPZ
Data product custodian	IDVMPZ
Name of the Schema file	euc-le3-id-vmpz-MOCVisibilityMask.xsd
Last Edited for DPDD Version	2.0
Processing Element(s) creating/using the data product	Creators: VMPZ_Visibility (LE3_VMPZ_ID_Visibility) Consumers: VMPZ_Random (LE3_VMPZ_ID_Random)
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:visibilityMaskMOCVMPZ
QualityFlags	object of type dqc:sqfPlaceHolder
Parameters	object of type ppr:genericKeyValueParameters

Detailed Description of the Data Product

This output product is a MOC Partial map collecting, at a given position of the sky and for a given type/redshift bin, the excess or deficit of galaxies with respect to the mean density (= density contrast) assumed to be related to systematic effects.

It includes the VisibilityMaskMOC metadata, a container with a FITS file (of type le3.id.vmpz.mocvisibilitymask) describing the visibility map for the survey in MOC HEALPix format, 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 VisibilityMaskMOCParams 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
	DEPTHEST	Estimator of depth	string
	SEL	Whole galaxy selection string.	string
	BINSEL	ID of galaxy sample/bin selection	string
	SOFTNAME		string
	SOFTVERS		string
	SOFTINST		string

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: combination of bits reported in the bitmask (32 binary digits, each 0 or 1, following the standard most significant bit first convention) [StringKeyword]

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

12. SEL: Galaxy selection string (empty if not applicable) [StringKeyword]

13. BINSEL: Identifier for the selection of the bin/population [StringKeyword]

and basic software parameters:

1. SOFTNAME: name of software used [StringKeyword]

2. SOFTVERS: version of software used [StringKeyword]

3. SOFTINST: institute developing the software [StringKeyword]

Partial MOC Footprint Table (First Extension, Binary Table)

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

HDU VISIBILITY_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
	MOCORDER		integer
	MOCTYPE		string
	EXTNAME		string

HDU VISIBILITY_MASK: 3 columns table
	Name	Description	Unit	Format
Columns	UNIQ	Index of the HEALPix pixel cell	NA	FITS K
	WEIGHT	Depth	NA	FITS E
	ERROR	Mask error value	NA	FITS E

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

9. MOCORDER (best HEALPix order) [IntegerKeyword]

The table is then expected to contain the following columns:

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

2. WEIGHT: (floating-point) weight in [0,1] giving the probability of detection of a given population/bin [E, float32]