Difference: HistoMergingProd (1 vs. 3)

Revision 32017-04-13 - MarcoCorvo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
Production to merge histograms are slightly different from normal data processing ones. There are two different type of input files to consider: BRUNELHIST and DAVINCIHIST, so in the Input Data section of the request, it must be selected both file types.

  • Screenshot of the Histo Merging request:
    HistoMerge.PNG
Changed:
<
<
The template to choose is everyThingElse_run.py. Type Merge as production to be launched, GroupSize must be equal to 999999, as we create one single merged file per run. Output Data Storage Element must be CERN-HIST-EOS. The plugin name must be ByRunSizeWithFlushRootMerging and the removeInputs flag must be set to True in order to delete the unmerged files.
>
>
The template to choose is everyThingElse_run.py. Type HistoMerge as production to be launched, GroupSize must be equal to 999999, as we create one single merged file per run. Output Data Storage Element must be CERN-HIST-EOS. The plugin name must be ByRunSizeWithFlushRootMerging and the removeInputs flag must be set to True in order to delete the unmerged files.
 

-- MarcoCorvo - 2016-10-19

Revision 22017-01-24 - MarcoCorvo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
Production to merge histograms are slightly different from normal data processing ones. There are two different type of input files to consider: BRUNELHIST and DAVINCIHIST, so in the Input Data section of the request, it must be selected both file types.

  • Screenshot of the Histo Merging request:
    HistoMerge.PNG
Changed:
<
<
The template to choose is everyThingElse_run.py. Type Merge as production to be launched, then in the Custom Module List add GaudiApplication, AnalyseXMLSummary, BookkeepingReport, StepAccounting. The GroupSize must be kept quite "high", e.g. 50 and as Output Data Storage Element it should be put CERN-HIST-EOS. The plugin name must be ByRunSizeWithFlushRootMerging and the removeInputs flag must be set to True in order to delete the unmerged files.
>
>
The template to choose is everyThingElse_run.py. Type Merge as production to be launched, GroupSize must be equal to 999999, as we create one single merged file per run. Output Data Storage Element must be CERN-HIST-EOS. The plugin name must be ByRunSizeWithFlushRootMerging and the removeInputs flag must be set to True in order to delete the unmerged files.
 

-- MarcoCorvo - 2016-10-19

Revision 12016-10-19 - MarcoCorvo

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbComputing"
Production to merge histograms are slightly different from normal data processing ones. There are two different type of input files to consider: BRUNELHIST and DAVINCIHIST, so in the Input Data section of the request, it must be selected both file types.

  • Screenshot of the Histo Merging request:
    HistoMerge.PNG

The template to choose is everyThingElse_run.py. Type Merge as production to be launched, then in the Custom Module List add GaudiApplication, AnalyseXMLSummary, BookkeepingReport, StepAccounting. The GroupSize must be kept quite "high", e.g. 50 and as Output Data Storage Element it should be put CERN-HIST-EOS. The plugin name must be ByRunSizeWithFlushRootMerging and the removeInputs flag must be set to True in order to delete the unmerged files.

-- MarcoCorvo - 2016-10-19

META FILEATTACHMENT attachment="HistoMerge.PNG" attr="" comment="Screenshot of the Histo Merging request" date="1476887275" name="HistoMerge.PNG" path="HistoMerge.PNG" size="31477" user="corvo" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback