.. _MERConfigurationSet:
  
Configuration Set Product
-------------------------
  
Data product name
=================
.. DataProductNameStart
   
DpdMerConfigurationSet
   
.. DataProductNameEnd
   
Data product custodian
======================
.. DataProductCustodianStart
   
MER
   
.. DataProductCustodianEnd
   
Data model tag
==============
.. DataModelTagStart
   
9.0.2
   
.. DataModelTagEnd
   
Name of the Schema file
=======================
.. NameSchemaStart
   
euc-test-mer-ConfigurationSet.xsd
   
.. NameSchemaEnd
   
Schema documentation tag
========================
.. SchemaDocTagStart
   
:emphasis:`Documentation for data product element DpdMerConfigurationSet:`
    
MER configuration set. This product is an input to the MER processing function.
It can contain a list of one or more configuration files to be used instead of
the default configuration files (those that are distributed together with the 
pipeline code). For example, it could contain a configuration file that sets
some of the swarp parameters to be used in the MER mosaic production module.
   
.. SchemaDocTagEnd
   
Data product elements
=====================
.. DataProductElementsStart
   
Header of type: sys:genericHeader

Data of type: mer:merConfigurationSet

QualityFlags of type: dqc:sqfPlaceHolder

Parameters of type: ppr:genericKeyValueParameters

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

Creators:

* None. This is an input product that is generated manually or using some
  dedicated scripts.
  
Consumers:
 
* All the MER :term:`Processing Element`\s.

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

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

This is an input product to the MER :term:`Pipeline`. It can contain a list of
one or more configuration files to be used instead of the default configuration
files (those that are distributed together with the pipeline code).

The main elements inside this product are:

* **TileIndex** (optional): The MER tile index to which the configuration set
  should be associated.
* **PatchId** (optional): The sky patch id to which the configuration set should
  be associated.
* **ProcessingMode** (optional): The MER pipeline processing mode (WIDE or
  DEEP) to which the configuration set should be associated.
* **ConfigurationFile** (one to infinity): Element containing the module name 
  and a link to the configuration file to be used for that module.
* **Comment** (optional): A comment describing this particular configuration 
  set (why it was created, why we are not using the default configuration 
  files, etc).

.. DetailedDescEnd