Bug in file metadata for output data of a production
Currently, for a given production, file metadata are set to the output data of each step only if they are explicitely specified in the input query or in the job configuration.
However we would like that if the following metadata : nsb, div_ang are defined for the input data of a given step, they should also be set to the output data with the same value, even if they are not explicitely specified in the input query or in the job configuration.
In order to clarify, currently the following configuration file:
ProdSteps:
- ID: 1
input_meta_query:
parentID:
MCCampaign: PROD5b
array_layout: Alpha
site: LaPalma
particle: electron
thetaP: 20.0
phiP: 180.0
analysis_prog: ctapipe-process
analysis_prog_version: v0.19.0
data_level: 2
outputType: Data
configuration_id: 8
merged: 0
job_config:
type: Merging
version: v0.19.0
group_size: 50
output_extension: merged.DL2.h5
Common:
MCCampaign: PROD5b
configuration_id: 8
base_path: /vo.cta.in2p3.fr/MC
builds a production with a Merging step which takes DL2 files as input. These DL2 files have nsb=1 (even if nsb=1 has not been specified in the inputquery), but the output files of this Merging step do not have any nsb set.
Now we would like that if nsb is set for the input files, it should be also set=1 for the output files.
Idem for div_ang.