.. include:: ../../idsubstitutions.txt
.. _VMPZIDRandomCatalog:

Output Product: Photometric Random Catalog
------------------------------------------

Data product name
=================
.. DataProductNameStart

VMPZIDRandomCatalog

.. DataProductNameEnd

Data product custodian
======================
.. DataProductCustodianStart

VMPZ-ID

.. DataProductCustodianEnd

Data model tag
==============
.. DataModelTagStart

|ML2A2BF|

.. DataModelTagEnd

Name of the Schema file
=======================
.. NameSchemaStart

|ML2A2BF|

.. NameSchemaEnd

Schema documentation tag
========================
.. SchemaDocTagStart

|ML2A2BF|

.. SchemaDocTagEnd

Data product elements
=====================
.. DataProductElementsStart

|ML2A2BF|

.. DataProductElementsEnd

Processing Element(s) creating/using the data product
=====================================================
.. PECreatorStart

2PCF-WL

.. PECreatorEnd

Processing function using the data product
==========================================
.. PFUsingStart

LE3

.. PFUsingEnd

Detailed description of the data product
========================================
.. DetailedDescStart

This output product is a photometric random catalogue.

It is an extension of a base catalogue, includes the **RandomCatalog** metadata,
a container with a FITS file (of type le3.id.vmpz.randomcatalog), and the mask
parameters **RandomParams** 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:

#. **DATE-OBS**: start of observation with format 'yyyy-mm-ddThh:mm:ss.sss' [StringKeyword]
#. **DATE-END**: end of observation with format 'yyyy-mm-ddThh:mm:ss.sss' [StringKeyword]
#. **TELESCOP**: name of the telescope [StringKeyword]
#. **INSTRUME**: name of the instrument [StringKeyword]
#. **FILTER**: name of the filter [StringKeyword]
#. **FILTLST**: selection of filter if intersection of multiple footprints [StringKeyword]
#. **TILEID**: identifier of the MER Tile processed (-1 if multiple Tiles) [IntegerKeyword]
#. **LISTID**: identifier of a MER list of tiles product (-1 if single Tile) [StringKeyword]
#. **NSIDE_WK**: Nside parameter used for frame->HEALPix [StringKeyword]
#. **BITSEL**: identifier of the bit of combination of bits used in the depth map
   (e.g. 0 for least significant bit,..,18) [StringKeyword]
#. **DEPTHEST**: estimator used for depth computation [StringKeyword]
#. **BINSEL**: Identifier for the selection of the bin/population [StringKeyword]

   and basic software parameters:

#. **SEED**:Seed used for random generations[StringKeyword]
#. **NSIMOBJ**:Number of simulated objects in the catalogue [IntegerKeyword]
#. **SOFTNAME**: name of software used [StringKeyword]
#. **SOFTVERS**: version of software used  [StringKeyword]


Random Catalogue Table (First Extension, Binary Table)
++++++++++++++++++++++++++++++++++++++++++++++++++++++

#. **SIM_ID**: Galaxy Simulated Id [K, int64]
#. **RIGHT_ASCENSION**: Right ascension (*in degrees*) [D, float64]
#. **DECLINATION**: Declination (*in degrees*) [D, float64]
#. **TOM_BIN_ID**: ID of selection bin [J, int32]
#. **WEIGHT**: weight associated to the galaxy (probability of detection?) [E, float32]

.. note::
   Do we really need a SIM_ID? Ben said that it could be useful if we want to subselect several
   sub-catalogs from a master one if I remember well

.. note::
   The weight column is not clear: does it give a probability of detection in a tomographic bin, or the weight
   associated to a galaxy for mitigating systematics effects/improving SNR  as for the
   photometric galaxy clustering ?- with recipe not yet fixed in WL-

.. note::
   Assigning the TOM_BIN_ID implies knowing the probability of assigning a detected galaxy
   from a given galaxy population to a given TOM_BIN_ID and should imply not yet identified products from PHZ.

.. note::
   Here this is a random catalogue associated to a given selection, not a master catalogue
   where selection can be applied. But the photometric galaxy clustering use case should lead
   to a quite stable selection. Other possibility is to encode selection in the TOM_BIN_ID,
   and then further subselect on this.

.. DetailedDescEnd