Clusters Detection Output Product from PZWAV

Data product name

detclClusters

Data product custodian

DET-CL

Data model tag

DpdLE3clDetClusters

Name of the Schema file

euc-test-le3-cl-detcl-clusters.xsd

Schema documentation tag

This output product contains the catalog of PZWAV candidate clusters

Data product elements

Header

type sys:genericHeader

Data

type cl:detectedDETClusters

QualityFlags

type dqc:sqfPlaceHolder

Parameters

type ppr:genericKeyValueParameters

Processing Element(s) creating/using the data product

DET-CL

Processing function using the data product

LE3, “DET-CL” pipeline

Detailed description of the data product

XML Keywords

The metadata provided with the output FITS contains the following keywords:

KEYWORDS COMMON TO BOTH DETECTION CODES: GENERAL PARAMETERS

  1. MIN_Z: lower limit of redshift range for cluster detection

  2. MAX_Z: upper limit of redshift range for cluster detection

  3. MIN_RA: Minimum RA of the area on which the run has to be performed [deg]

  4. MAX_RA: Maximum RA of the area on which the run has to be performed [deg]

  5. MIN_DEC: Minimum Dec of the area on which the run has to be performed [deg]

  6. MAX_DEC: Maximum Dec of the area on which the run has to be performed [deg]

  7. SNR_THR: the S/N threshold for extracting a detection

KEYWORDS SPECIFIC TO AMICO DETECTION CODE:

  1. CUBE_XY_STEP: size of the RA and Dec bin [deg]

  2. MAX_AREA_DEG: Maximum area for a single tile on which AMICO can run [deg^2]

  3. L_BORDER_DEG: Size of the border defining the detection area [deg]

KEYWORDS SPECIFIC TO PZWAV DETECTION CODE:

  1. DZ: half width of reach redshift slice

  2. ZSTEP: interval between slices

  3. KRN_SCL1: lower scale of kernel, in kpc

  4. KRN_SCL2: larger scale of kernel, in kpc

  5. DR_LIM: radius of matching area for the merging of detected peaks, in kpc

  6. DZ_LIM: redshift depth for the merging of detected peaks

  7. FROM_DENSITY_MAP: if True, indicates that a previously computed density map should be used as an input, therefore bypassing the first stages of PZWAV

COSMOLOGY PARAMETERS KEYWORDS:

  1. OMEGA_MAT: matter energy density

  2. OMEGA_VAC: vacuum energy density

  3. HUBBLE_PAR: Hubble constant in km/s/(Mpc/h)

  4. W_EQ_STATE: dark energy equation of state

  5. N_EFF: effective number of relativistic species

  6. TEMP_CMB: CMB temperature

Note : Currently, a flat LCDM model is assumed, depending only on HUBBLE_PAR and OMEGA_MAT. The list above allows a broader choice for the cosmological model (wCDM).

KEYWORDS FOR RICH-CL TO MOVE TO THE CCP PIPELINE:

  1. MAX_NB: Maximum number of structures to which a galaxy can be associated

  2. MIN_PROB: Minimum probability for the association to be saved

Clusters FITS file

The FITS file produced by DET-CL contains the following keywords:

Keywords

This fits file is expected to contain the following keywords in the data table HDU, characterising the main parameters of the “clusters detection” product.

COSMOLOGY PARAMETERS KEYWORDS

  1. OMEGA_MAT: matter energy density

  2. OMEGA_VAC: vacuum energy density

  3. HUBBLE_PAR: Hubble constant in km/s/(Mpc/h)

  4. W_EQ_STATE: dark energy equation of state

  5. N_EFF: effective number of relativistic species

  6. TEMP_CMB: CMB temperature

Note : Currently, a flat LCDM model is assumed, depending only on HUBBLE_PAR and OMEGA_MAT. The list above allows a broader choice for the cosmological model (wCDM).

KEYWORDS COMMON TO BOTH DETECTION CODES: GENERAL PARAMETERS

  1. DET_CODE: Name of the detection algorithm (AMICO or PZWAV)

  2. MIN_Z: lower limit of redshift range for cluster detection

  3. MAX_Z: upper limit of redshift range for cluster detection

  4. MIN_RA: Minimum RA of the area on which the run has to be performed [deg]

  5. MAX_RA: Maximum RA of the area on which the run has to be performed [deg]

  6. MIN_DEC: Minimum Dec of the area on which the run has to be performed [deg]

  7. MAX_DEC: Maximum Dec of the area on which the run has to be performed [deg]

  8. SNR_THR: the S/N threshold for extracting a detection

KEYWORDS SPECIFIC TO AMICO DETECTION CODE (same keywords as in detclParameters):

  1. CUBE_XY_STEP: Size [deg] of the Amplitude bins in the X- and Y-dimensions

  2. MAX_AREA_DEG: Maximum area [deg^2] allowed for a detection-tile

  3. L_BORDER_DEG: Size [deg] of the border around a detection-tile

  4. MODEL_ID: Name that identifies the adopted model

KEYWORDS SPECIFIC TO PZWAV DETECTION CODE (same keywords as in detclParameters):

  1. DZ: half width of reach redshift slice

  2. ZSTEP: interval between slices

  3. KRN_SCL1: lower scale of kernel, in kpc

  4. KRN_SCL2: larger scale of kernel, in kpc

  5. PIX_DEG: number of sampling pixels per degree

  6. DR_LIM: radius of matching area for the merging of detected peaks, in kpc

  7. DZ_LIM: redshift depth for the merging of detected peaks

  8. FROM_DENSITY_MAP: if True, indicates that a previously computed density map was used as an input, therefore bypassing the first stages of PZWAV

Table

The table of the “detclClusters” product is expected to contain the following columns, for each detected cluster :

Column name

Description

Unit

ID_CLUSTER

Identifier number of the detected cluster

RIGHT_ASCENSION_CLUSTER

Right Ascension coordinate (J2000) of the cluster center

deg

DECLINATION_CLUSTER

Declination coordinate (J2000) of the cluster center

deg

Z_CLUSTER

Redshift estimate of the cluster

Z_ERR_CLUSTER

Error associated to the cluster redshift estimate

SNR_CLUSTER

Signal-to-noise ratio of the detection

SNR_UNIQUE_CLUSTER

Signal-to-noise ratio of the detection, from a common definition

RADIUS_CLUSTER

Angular radius associated to the detected cluster

arcmin

RICHNESS_CLUSTER

Absolute richness estimator of the detected cluster

FRAC_MASKED_CLUSTER

Fraction of the cluster area (=f(center,radius)) covered by visibility mask

LAMBDA_STAR_CLUSTER

Lambda star observable

FLAG_EDGE_CLUSTER

Flag stating if the detection is at border of a mask or a field limit

The SNR_CLUSTER, RADIUS_CLUSTER, and RICHNESS_CLUSTER quantities may have different definitions depending on the considered detection code. The user should refer to the SDD and scientific documentation of the corresponding code.