Output Product: MOC Depth Map

$SetSchemaPath le3/id/vmpz/out/euc-le3-id-vmpz-MOCDepthMap.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 is a partial MOC map collecting the depth maps.

It includes the DepthMapMOC metadata, a container with a FITS file (of type le3.id.vmpz.mocdepthmap) describing the depth map for the survey in MOC 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 DepthMapMOCParams 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.mocdepthmap

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

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

$PrintHDUTableContents fit/euc-le3-id.xml le3.id.vmpz.mocdepthmap DEPTH_MAP

  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. MOCORDER (best HEALPix order) [IntegerKeyword]

  9. MOCTYPE [StringKeyword]

  10. DATE [StringKeyword]

  11. EXTNAME (= ‘DEPTH_MAP’) [StringKeyword]

The table is then expected to contain the following columns:

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

  2. WEIGHT: (floating-point) weight associated to pixel indicating the depth [E, float32]

Note

Should add keywords for galaxy type if input parameters