Output Product: COSEBI for Cosmic Shear

$SetSchemaPath le3/wl/twopcf/out/euc-le3-wl-twopcf-COSEBIShearShear2D.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:

  • LE3_2PCF_WL_ShearShear_Pipeline

  • LE3_CM_2PCF_WL_ShearShear_Pipeline

Consumers:

  • WL-SWG

Processing Function using the products

SGS pipeline output product to be used by LE3 and SWGs

Proposed for inclusion in EAS/SAS

This product is proposed for inclusion in the SAS: Yes

Motivation: the product contains the two-point shear-shear tomographic real-space second order statistic EE,BB,EB functions requested by the RSD document.

Data Product Elements

$PrintDataProductElements

Detailed Description of the Data Product

This product contains the tomographic cosmic shear COSEBI modes. This output product is a fits file (see le3.wl.2pcf.output.cosebishearshear2d in the following FITS descriptors).

Extra (optional) metadata associated to the FITS container are the following:

  • SpatialCoverage a description of the spatial footprint [optional, cot:spatialFootprint],

  • CatalogSelection: describing the selection in the input catalogues [optional, up to 2 elements]

    • CatalogFileName: the name of the input catalogue [sys:dataFileName]

    • CatalogSHE: type of input catalogue [string among “BFD”, “KSB”, “LensMC”,”MomentsML”,”REGAUSS”,”MER_PHZ”, “OTHER” ]

    • Selection: selection associated to catalogue [string]

    • CatalogUse: for which use case the catalog is employed (=[“ShearShear”]) [string among “PosPos”, “PosShear”, “ShearShear”]

    • CatalogInfo: whether position or shear information is used in this catalogue [string among “Pos”, “Shear”] (=[“Shear”])

    • CatalogOrder: order associated to catalogue for reporting (e.g. BIN_ID1)[int32]

The fits file contains:

  • a primary array containing important computation parameters as keywords,

  • binary tables in the next HDUs with COSEBIs for specific redshift bins.

Primary Array

This fits table is expected to contain the following keywords in primary HDU, characterizing the important parameters of the product:

$PrintPrimaryHeader fit/euc-le3-wl.xml le3.wl.2pcf.output.cosebishearshear2d

  1. THMIN: minimal angular value chosen for spatial binning [DoubleKeyword]

  2. THMAX: maximal angular value chosen for spatial binning [DoubleKeyword]

  3. OATH: maximal open angle value used for the approximation [DoubleKeyword]

  4. THUNIT: unit of spatial distance [StringKeyword]

  5. BINSCALE: if linear or logarithmic scales are used for output [StringKeyword]

  6. COORDSYS: if spherical or cartesian computation of distances [StringKeyword]

  7. NMODES: number of COSEBI modes [IntegerKeyword]

  8. SHE_SOFT: which SHE catalogue used [StringKeyword]

  9. SHE_SEL: selection for shear catalogue [StringKeyword]

  10. SOFTNAME: name of software used for COSEBI [StringKeyword]

  11. SOFTVERS: version of software used for COSEBI [StringKeyword]

Table (HDU=1…)

The following keywords are added to the header of the HDUs:

$PrintHDUTableContents fit/euc-le3-wl.xml le3.wl.2pcf.output.cosebishearshear2d SHEARSHEAR2D_COSEBI_n

  1. BIN_ID1: bin for first catalog [IntegerKeyword]

  2. BIN_ID2: bin for second catalog [IntegerKeyword]

  3. EXTNAME: “SHEARSHEAR2D_COSEBI”

and the columns are:

  1. MODE: COSEBI mode [I,int16]

  2. EE: E mode COSEBI [D, float64]

  3. BB: B mode COSEBI [D, float64]

  4. EB: E/B mode COSEBI [D, float64]

Note

Under discussion is the possibility of having as first HDU a summary table to allow fast access to the HDU corresponding to a particular bin combination:

  1. BIN_ID1: bin for first catalog [J, int32]

  2. BIN_ID2: bin for second catalog [J, int32]

  3. HDU: HDU index [J, int32]