Output Product: Tomographic Angular Power Spectra

Metadata

Data product name	DpdTwoPCFWLClPosPos2D
Data product custodian	WLTWOPCF
Name of the Schema file	`euc-le3-wl-twopcf-ClPosPos2D.xsd <https://gitlab.euclid-sgs.uk/ST-DM/ST_DataModel/-/blob/10 .1.2/ST_DM_Schema/auxdir/ST_DM_Schema/dpd/le3/wl/twopcf/out/euc-le3-wl-twopcf-ClPosPos2D.xsd >`_
Last Edited for DPDD Version	1.1
Processing Element(s) creating/using the data product	Creators: LE3_2PCF_WL_PosPosEstimator_Pipeline LE3_CM_2PCF_WL_PosPosEstimator_Pipeline LE3_2PCF_WL_PosPos_Pipeline LE3_CM_2PCF_WL_PosPos_Pipeline Consumers: WL-SWG
Processing function using the data product	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 position-position tomographic real-space second order statistic CL functions requested by the RSD document.

Data Product Elements

Header	object of type sys:genericHeader
Data	object of type wl2pcf:twoPCFWLClPosPos2D
QualityFlags	object of type dqc:sqfPlaceHolder
Parameters	object of type ppr:genericKeyValueParameters

Detailed Description of the Data Product

This product contains the tomographic angular power spectra.

This output product is a fits file (see le3.wl.2pcf.output.clpospos2d 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 (=[“PosPos”]) [string among “PosPos”, “PosShear”, “ShearShear”]

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

  • 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 angular power spectra 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:

HDU PRIMARY: header
	Name	Description	Value
Keywords	SIMPLE		logical
	BITPIX		integer
	NAXIS		integer
	EXTEND		logical
	W_EST		string
	THMIN	Min of angular range	double
	THMAX	Max of angular range	double
	OATH	Open Angle threshold	double
	THUNIT	Unit of theta	string
	BINSCALE	lin or log bins	string
	COORDSYS	cartesian or spherical	string
	SHE_SOFT	Where the input catalogue is coming from (if SHE catalogue used)	string
	POS_SEL	ID of selection made (e.g. tomographic redshifts, stellar mass)	string
	SOFTNAME		string
	SOFTVERS		string
	BLINDING	Flag that identifies products that have been blinded for scientific analysis	string

1. W_EST: choice of estimator (Landy-Szalay or Hamilton or DD, DR, RR) [StringKeyword]

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

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

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

5. THUNIT: unit of spatial distance [StringKeyword]

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

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

8. SHE_SOFT: which SHE catalogue used (if used) [StringKeyword]

9. POS_SEL: selection for position catalogue [StringKeyword]

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

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

Table (HDU=1…)

HDU POSPOS2D_CL_n: 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
	TTYPE4		string
	TFORM4		string
	EXTNAME		string
	BIN_ID1	First Bin in Correl	integer
	BIN_ID2	Second Bin in Correl	integer

HDU POSPOS2D_CL_n: 4 columns table
	Name	Description	Unit	Format
Columns	ELL		NA	FITS D
	CL		NA	FITS D
	ELL_LOWER		NA	FITS D
	ELL_UPPER		NA	FITS D

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

1. BIN_ID1: bin for first catalog [IntegerKeyword]

2. BIN_ID2: bin for second catalog [IntegerKeyword]

3. EXTNAME: “POSPOS2D_CL”

and the column is:

1. ELL: central multipole in the band [D, float64]

2. CL: band power spectrum [D, float64]

3. ELL_LOWER: minimal multipole in the band [D, float64]

4. ELL_UPPER: maximal multipole in the band [D, float64]

Note

Under discussion is the possibility in the future of having as first HDU a summary table with information on the binning for spectra tables (HDU>2):

1. ELL: mean multipole in the band [D, float64]

2. ELLMIN: minimal multipole in the band [D, float64]

3. ELLMAX: maximal multipole in the band [D, float64]

and in the second 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]

Warning

We have discussed to add later in the primary header

<IntegerKeyword name="POS_SEL"/> <!-- ID of selection made (e.g. tomographic redshifts, stellar mass…) -->