html>
Production models for MC11a
Productions models for MC for 2011 data (a.k.a. MC11a)
A set of models have been prepared to cover the various needs for the MC productions for 2011 data (a.k.a. MC11a).
The models fix the simulation conditions, applications configuration,
define the steps and combine the steps for the whole processing of the MC
production and are transformed in workflows by the production managers.
The Ph WG can use the models or modify them for their needs.
Additional steps for special needs (e.g. using a different generator) are setup
on demand. Contact the lhcb-gauss-manager@cern.ch for this.
There are four simulation conditions corresponding to the beam and
detector conditions with which we collected most of the data in 2011:
- magnet up and magnet down,
- with and without spillover.
This implies that all applications need to have at least two steps defined for
the two SIMCOND tags to be used corresponding to magnet up and magnet down.
While for Gauss this also reflects into different options, for all other
applications this is the only difference.
Gauss and Boole need special options to handle generating events with
spill-over, hence two more steps are defined for each. Brunel, Moore and
DaVinci do not need special options for spill-over, i.e. the same configuration
handles both cases).
Merging only transfer the data and a single step is sufficient as it is not
necessary to set DDDB and CondDB tags.
When a different generator that Pythia is used for the production of the events, this is also specified in the simulation conditions. Currently two other generators are available for B_c and Chi_cc
The various simulation conditions set up are:
- Beam3500GeV-2011-MagDown-Nu2-EmNoCuts
- Beam3500GeV-2011-MagUp-Nu2-EmNoCuts
- Beam3500GeV-2011-MagDown-Nu2-50ns-EmNoCuts
- Beam3500GeV-2011-MagUp-Nu2-50ns-EmNoCuts
- Beam3500GeV-2011-MagDown-Nu2-EmNoCuts-BcVegPy
- Beam3500GeV-2011-MagUp-Nu2-EmNoCuts-BcVegPy
- Beam3500GeV-2011-MagDown-Nu2-EmNoCuts-GenXicc
- Beam3500GeV-2011-MagUp-Nu2-EmNoCuts-GenXicc
where 1 & 2 are without spill-over and 3 & 4 with spill-over with 50 ns bunch spacing. Conditions 5 & 6 are as 1 & 2 but using BcVegPy as generator instead of Pythia6. The same is for conditions 7 & 8 where the generator used in GenXicc instead.
In additions some simulation conditions for using Pythia at different energies
are also available:
- Beam1380GeV-2011-VeloClosed5mm-MagDown-Fix1-EmNoCuts
- Beam1380GeV-2011-VeloClosed5mm-MagUp-Fix1-EmNoCuts
FYI to read the simulation conditions you
- first have the beam energy,
- then the date of the experimental conditions (beam+detector) simulated,
- the nu (i.e the mean of the poisson of the number of pile-up events taking
into account all processes - the visible number of pileup, mu is related to
it by a simple formula mu = 0.7*nu )
- then the spill-over bunch spacing is present
- and last the Gauss/G4 setting).
For MC10 the experimental conditions were Oct2010, but in 2011 they were rather
stable from July to October, so only the year is listed.
Note that the simulation conditions are reflected in the Gauss and Boole
options so one has to be careful that the Gauss/Boole steps match the chosen
simulation conditions. This is done for the models provided.
There are two processing in
flagging mode for MC11a specifiyng
if the prescale is applied in the stripping or not.
Prescale is
never applied in the trigger.
It is up to the Phys WG do decide which production is more appropriate for
their needs when submitting a request.
A third processing will be set up to produced events in filtering (aka
rejection) mode: this will be accomplished by an additional DaVinci step
to be provided by the Phys WG for specific requests. Note that samples for
which the production request (i.e. the number of events to be processed before
rejection) is bigger than 10 M must have this additional step to be accepted.
The sequence of applications in the processing passes are:
- Gauss -> Boole -> Moore (in flagging mode) -> Brunel -> DaVinci (in flagging mode w pre-scale) [-> Merging] (the Merging is a technical step at the end)
- Gauss -> Boole -> Moore (in flagging mode) -> Brunel -> DaVinci (in flagging mode w/o pre-scale) [-> Merging]
For the case when a Ph WG wants to run in rejection mode the processing pass
will be: p1 + an additional DaVinci WG stripping including possible filtering
at the trigger level, explicitely this will be
- Gauss -> Boole -> Moore (in flagging mode) -> Brunel -> DaVinci (in flagging mode w pre-scale) -> DaVinci WG trig & strip rejection [-> Merging]
For this last case an accounting of the number of events
produced/rejected/retained has to be put in place. The Charm Phys WG is
setting up and testing an example that will be provied as model.
The database tags are fixed for MC 2011 and define the geometry layout and the
conditions for the 2011 detector. The database may in some cases include
technical changes needed for running with the newest code older configurations
(e.g. 2010). In case additional conditions are wanted (e.g. 2010,
velo partially open, magnet off) contact lhcb-gauss-manager@cern.ch.
In order to fix a bug for caloPID calibrations and to include some missing materials a new set of database tags for 2011 has been introduced in July 2011. This correspond to a new simulation processing step Sim05c since the samples will be slitghtly different that those produced with earlier processing.
DDDB tag & CondDB (=SIMCOND) tags
- For Sim05c, Sim05d:
- DDDBtag = MC2011-20120727
- CondDBtag = MC2011-20120727-vc-md100 (for magnet down)
- CondDBtag = MC2011-20120727-vc-mu100 (for magnet up)
-
- For Sim05, Sim05a, Sim05b:
- DDDBtag = MC11-20111102
- CondDBtag = sim-20111111-vc-md100 (for magnet down)
- CondDBtag = sim-20111111-vc-mu100 (for magnet up)
The simulation conditions and the processing passes are used to identify the
datasets produced in the book-keeping database.
A given step define the options and database tags,
but there may be more then one step where the difference
is rather in the Simulation Conditions. For this reason in addition to a name
to help identifing a step when setting up a production request,
there is a
processing pass that identify the group of steps with the same
application and options independend of the simulation conditions.
The
processing pass appears in the book-keeping path and
it is indicated below in the models.
Below is the list of models prepared and their explanation (note that the processing pass in square braket is not visible in the book-keeping path):
Contact the Simulation Application Managers if you need to increase statistic produced with earlier version of Gauss or database tags or in case a model to produce what you want is not listed..
| Request Id
| Name
| Sim/Run conditions
| Processing pass
| Steps
|
| 5285
| MC11a Model - MD - Trig and Strip flagged
| Beam3500GeV-2011-MagDown-Nu2-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 124437 + 17896 + 17899 + 17894 + 17902 + 16018
|
| 5286
| MC11a Model - MU - Trig and Strip flagged
| Beam3500GeV-2011-MagUp-Nu2-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 124438 + 17895 + 17900 + 17893 + 17901 + 16018
|
| 5287
| MC11a Model - MD - Trig and Strip flagged, Strip prescaled
| Beam3500GeV-2011-MagDown-Nu2-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17Flagged[/Merge12]
| 124437 + 17896 + 17899 + 17894 + 17904 + 16018
|
| 5288
| MC11a Model - MU - Trig and Strip flagged, Strip prescaled
| Beam3500GeV-2011-MagUp-Nu2-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17Flagged[/Merge12]
| 124438 + 17895 + 17900 + 17893 + 17903 + 16018
|
| 5220
| MC11a Model - MD - BcVegPy - Trig and Strip flagged
| Beam3500GeV-2011-MagDown-Nu2-EmNoCuts-BcVegPy
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 124376 + 17896 + 17899 + 17894 + 17902 + 16018
|
| 5222
| MC11a Model - MU - BcVegPy - Trig and Strip flagged
| Beam3500GeV-2011-MagUp-Nu2-EmNoCuts-BcVegPy
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 124377 + 17895 + 17900 + 17893 + 17901 + 16018
|
| 7777
| MC11a Model - MD - Xi_cc with GenXicc - Trig and Strip flagged
| Beam3500GeV-2011-MagDown-Nu2-EmNoCuts-GenXicc
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 17850 + 17896 + 17899 + 17894 + 17902 + 16018
|
| 7778
| MC11a Model - MU - Xi_cc with GenXicc - Trig and Strip flagged
| Beam3500GeV-2011-MagUp-Nu2-EmNoCuts-GenXicc
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 17849 + 17895 + 17900 + 17893 + 17901 + 16018
|
| 7779
| MC11a Model - MD - Xi_bc with GenXicc - Trig and Strip flagged
| Beam3500GeV-2011-MagDown-Nu2-EmNoCuts-GenXicc
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 17281 + 17896 + 17899 + 17894 + 17902 + 16018
|
| 7780
| MC11a Model - MU - Xi_bc with GenXicc - Trig and Strip flagged
| Beam3500GeV-2011-MagUp-Nu2-EmNoCuts-GenXicc
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 17282 + 17895 + 17900 + 17893 + 17901 + 16018
|
| 5289
| MC11a Model - MD - SpillOver - Trig and Strip flagged
| Beam3500GeV-2011-MagDown-Nu2-50ns-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 17852 + 17898 + 17899 + 17894 + 17902 + 16018
|
| 4612
| MC11a Model - MU - SpillOver - Trig and Strip flagged
| Beam3500GeV-2011-MagUp-Nu2-50ns-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17NoPrescalingFlagged[/Merge12]
| 17851 + 17897 + 17900 + 17893 + 17901 + 16018
|
| 4613
| MC11a Model - MD - SpillOver - Trig and Strip flagged, Strip prescaled
| Beam3500GeV-2011-MagDown-Nu2-50ns-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17Flagged[/Merge12]
| 17852 + 17898 + 17899 + 17894 + 17904 + 16018
|
| 4614
| MC11a Model - MU - SpillOver - Trig and Strip flagged, Strip prescaled
| Beam3500GeV-2011-MagUp-Nu2-50ns-EmNoCuts
| Sim05d[/Digi11]/Trig0x40760037Flagged/Reco12a/Stripping17Flagged[/Merge12]
| 17851 + 17897 + 17900 + 17893 + 17903 + 16018
|
Now to the details of the steps set up for MC11a. Note that for special
requests (e.g. different generator) only the step necessary for the variation
wrt the models above is setup. The person requesting the production will have
to replace the step in the model.
Gauss is always the first step in the MC production. It can also be the only
step in case of generator only productions.
The version of Gauss used for MC11a are v41r1 to v41r4
and of DecFiles v25r1 to DecFiles v25r24.
There is a Gauss step for each simulation conditions: the magnet polarity is set
by the SIMCOND tag but determines some of the beam parameters, so the options
must be syncronized.
In case the version of Gauss changes in a way that may affect the content of some
event types (e.g. change of the behaviour of a cut), then the letter for the processing
pass name is changed. In case the DecFiles version is changed to add new event types
that is not the case.
The processing pass used are called Sim05, Sim05a, Sim05b, Sim05c, Sim05d.
The differences are the following:
- Sim05
- - Gauss v41r1
- - DecFiles from v25r1 to v25r3
- -
database tags MC11-20111102 and sim-20111111-vc-m{d,u}100
- Sim05a
- - Bug fix for signal Ks to allow them to be produced from K0 removing bias on their momentum distribution.
- - Only some event type are affected.
- - Gauss v41r2 to v41r3
- - DecFiles from v25r4 to v25r11
- -
database tags MC11-20111102 and sim-20111111-vc-m{d,u}100
- - See Gauss v41r2 release documentaion for details.
- Sim05b
- - Bug fix in generator level cut LoKi::GenCut for oscillation flag, also bug fix for EvtGenExtra BTOSLLMS model
- - Only some event type are affected.
- - Gauss v41r4
- - DecFiles from v25r12
- -
database tags MC11-20111102 and sim-20111111-vc-m{d,u}100
- - See Gauss v41r4 release documentation for details.
- Sim05c
- - Bug fix in CaloPID calibration and added some missing material
- - All event types are affected.
- - Gauss v41r4
- - DecFiles from v25r12 to v25r15
- -
database tags MC2011-20120727 and MC2011-20120727-vc-m{d,u}100
- - See the explanation of the tags in the Database tags documentation for details
- Sim05d
- - Signal baryons like Lambda_b are produced with Signal Plain instead of Repeated Hadronization that was causing a bias in their angular distribution
- - Only signal baryons are affected.
- - Gauss v41r4
- - DecFiles v25r16 to v25r24
- - database tags MC2011-20120727 and MC2011-20120727-vc-m{d,u}100
- - See DecFiles v25r16 release doc for details.
-
The last available steps (in bold) are listed here with all history.
Only the next to last is still available in some cases (in bold) to allow completion of
productions in progress.
If you need to generate events in Sim05(a) conditions contact the Gauss Managers.
- 124437, Sim05d with Nu=2.0 (w/o spillover) - MD - MC11a,
for MagDown w/o spillover, with Gauss v41r4 and DecFiles v25r24
Replaces:
- Sim05d steps: 124374, 124160, 124138, 124074, 124000, 123894, 123756
- Sim05c steps: 123695, 18086, 17944, 17924
- Sim05b steps: 17847
- Sim05a steps: 17761, 17669, 17581, 17438, 17367,
17265, 17118, 16958
- Sim05 steps: 16858, 16758, 16498, 16278 and 15718
- 124438, Sim05d with Nu=2.0 (w/o spillover) - MU - MC11a,
for MagUp w/o spillover, with Gauss v41r4 and DecFiles v25r24
Replaces:
- Sim05d steps: 124375, 124161, 124139, 124075, 124001, 123895, 123757
- Sim05c steps: 123696, 18087, 17945, 17925
- Sim05b steps: 17848
- Sim05a steps: 17762, 17670, 17582, 17439, 17368,
17266, 17119, 16959
- Sim05 steps: 16859, 16759, 16518, 16318 and 15738
- 17852, Sim05d with Nu=2.0 (with spillover) - MD - MC11a,
for MagDown w spillover, with Gauss v41r4 and DecFiles v25r24
Replaces:
- Sim05a steps: 17122, 16962
- Sim05 steps: 16760, 16538, 16338 and 15698
- 17851, Sim05d with Nu=2.0 (with spillover) - MU - MC11a,
for MagUp w spillover, with Gauss v41r4 and DecFiles v25r24
Replaces
- Sim05a steps: 17123, 16963
- Sim05 steps: 16761, 16558, 16298 and 15699
The processing steps for using the BcVegPy generator instead of plain Pythia6 are:
- 124376, Sim05d with Nu=2.0 (w/o spillover) - MD - MC11a,
for MagDown w/o spillover and BcVegPy as generator, with Gauss v41r4 and DecFiles v25r24
Replaces:
- Sim05d steps: 123758
- Sim05c steps: 18102, 17440
- Sim05a steps: 17120, 16960
- Sim05 steps: 16778, 16478, 16258 and 16038
- 124377, Sim05d with Nu=2.0 (w/o spillover) - MU - MC11a,
for MagUp w/o spillover and BcVegPy as generator, with Gauss v41r4 and DecFiles v25r24
Replaces:
- Sim05d steps: 123759
- Sim05c steps: 18103, 17441
- Sim05a steps: 17121, 16961
- Sim05 steps: 16798, 16479 and 16259
The processing steps for using the GenXicc generator instead of plain Pythia6 are:
(note that different steps are needed for Xi_cc and Xi_bc)
- For Xi_cc signals
- 17850, Sim05d with Nu=2.0 (w/o spillover) - MD - MC11a,
for MagDown w/o spillover and GenXicc as generator, with Gauss v41r4 and DecFiles v25r24
Replaces:
- 17849, Sim05d with Nu=2.0 (w/o spillover) - MD - MC11a,
for MagUp w/o spillover and GenXicc as generator, with Gauss v41r4 and DecFiles v25r24
Replaces:
- For Xi_bc signals
- 17281, Sim05d with Nu=2.0 (w/o spillover) - MD - MC11a,
for MagDown w/o spillover and GenXicc as generator, with Gauss v41r4 and DecFiles v25r24
- 17282, Sim05d with Nu=2.0 (w/o spillover) - MD - MC11a,
for MagUp w/o spillover and BcVegPy as generator, with Gauss v41r4 and DecFiles v25r24
The options to set the beam parameters in the corresponding steps are:
- $APPCONFIGOPTS/Gauss/Beam3500GeV-md100-MC11-nu2.py
- $APPCONFIGOPTS/Gauss/Beam3500GeV-mu100-MC11-nu2.py
- $APPCONFIGOPTS/Gauss/Beam3500GeV-md100-MC11-nu2-50ns.py
- $APPCONFIGOPTS/Gauss/Beam3500GeV-mu100-MC11-nu2-50ns.py
In additions to the options to set the beam parameters, those for setting the
event type in production according to the request, the generator engine and
geant4 settings are specified for all steps above:
- 1/2/3/4 + $DECFILESROOT/options/@{eventType}.py + $LBPYTHIAROOT/options/Pythia.py + $APPCONFIGOPTS/Gauss/G4PL_LHEP_EmNoCuts.py
In case of a different generator the options are:
- 1/2/3/4 + $DECFILESROOT/options/@{eventType}.py + $LBGENROOT/options/Gen.py + $APPCONFIGOPTS/Gauss/G4PL_LHEP_EmNoCuts.py
where
Gen is replaced by
BcVegPy for example.
Steps have been made for simulations at 1380 GeV beam energy as collected in 2011. These are no longer available and
are given here as reference. If you need such a production contact the Gauss Managers.
- 15098, Sim05 w beam at 1380 GeV - MC - MC11a, for
MagDown with 1 fix collision per bunch crossing, with Gauss v41r1 and
DecFiles v25r1
- 16358, Sim05 w beam at 1380 GeV - MC - MC11a, for
MagUp with 1 fix collision per bunch crossing, with Gauss v41r1 and
DecFiles v25r1
The corresponding options to set the beam parameters are:
- $APPCONFIGOPTS/Gauss/Beam1380GeV-md100-MC11-fix1.py
- $APPCONFIGOPTS/Gauss/Beam1380GeV-mu100-MC11-fix1.py
For productions at 4000 TeV contacts the lhcb-gauss-manager.
Boole is the second step in the MC production.
The version of Boole used for MC11a is v23r1
Boole steps are set up for the magnet polarities, to pick the correct SIMCOND
tag and to instruct Boole if spill-over or not has to be applied.
The steps are independent of the processing pass, that is called Digi11
and is not visible in the book-keeping where it is included with Sim05.
The magnet polarity is set via the SIMCOND tag.
- 17898, Digi11 w spillover - MD - MC11a for MagDown w spillover
Replaces:
- 15758 with older database tags
- 17897, Digi11 w spillover - MU - MC11a for MagUp w spillover
Replaces:
- 15778 with older database tags
- 17896, Digi11 w/o spillover - MD - MC11a for MagDown w/o spillover
Replaces:
- 15798 with older database tags
- 17895, Digi11 w/o spillover - MD - MC11a for MagUp w/o spillover
Replaces:
- 15818 with older database tags
The Boole options are the following when there is no spill-over
- $APPCONFIGOPTS/Boole/Default.py + $APPCONFIGOPTS/L0/L0TCK-0x0037.py
and in case of spill-over the following is added to those above:
- 1 + $APPCONFIGOPTS/Boole/EnableSpillover-50ns.py
Moore is the third step in the MC production.
The version of Moore used for MC11a is v12r8g1
Moore steps are set for the magnet polarities, to pick the correct SIMCOND
tag.
The steps are independent of the processing pass.
There are two processing pass called
Trig0x40760037Flagged and Trig0x760037Flagged depending on the
TCK. Currently only steps 1 and 2 below are available with the latest database tags (for
TCK 0x40760037). In case you need the other TCK contact the Simulation Application Managers.
The options of Moore define the TCK to be run. Note that although Boole is
setup to run L0 this is run ALWAYS in MC production in Moore. This is to allow
the possibility to run Moore with a different TCK, in which case new steps
will need to be defined. Contact the trigger group if you need to do so.
- 17899, Trigger - TCK 0x40760037 Flagged - MD - MC11a, for MagDown, based on 0x00760037 with AcceptFraction of the lines set to 1, with AppConfig v3r120 (replaces 15998)
Replaces:
- 16379 with older database tags
- 17900, Trigger - TCK 0x40760037 Flagged - MU - MC11a, for MagUp, based on 0x00760037 with AcceptFraction of the lines set to 1, with AppConfig v3r120 (replaces 15999)
Replaces:
- 16298 with older database tags
- 16218, Trigger - TCK 0x760037 Flagged - MD - MC11a, for MagDown, identical to what run on real data
- 16219, Trigger - TCK 0x760037 Flagged - MU - MC11a, for MagUp, identical to what run on real data
The options for Moore are identical for a given TCK and are for example:
- $APPCONFIGOPTS/Moore/MooreSimProduction.py + $APPCONFIGOPTS/Conditions/TCK-0x40760037.py + $APPCONFIGOPTS/Moore/DataType-2010.py
Brunel is the fourth step in the MC production.
The version of Brunel used for MC11a is v41r1p1
Brunel steps are set for the magnet polarities, to pick the correct SIMCOND
tag.
The steps are independent of the processing pass and of simulation conditions.
The processing pass is called Reco12a.
The following steps are set up:
- 17894, Reco12a for MC11 - MagDown for MagDown (replaces Reco12-15618 to keep Trigger and Muon RAW event)
Replaces:
- 16578 with older database tags
- 17893, Reco12a for MC11 - MagUp for MagUp (replaces Reco12-15638 to keep Trigger and Muon RAW event)
Replaces:
- 16598 with older database tags
The options used are specific to MC but correspond to the latest re-processing
of the 2011 data (Reco12):
- $APPCONFIGOPTS/Brunel/DataType-2011.py + $APPCONFIGOPTS/Brunel/MC-WithTruth.py + $APPCONFIGOPTS/Brunel/MC11a_dedxCorrection.py + $APPCONFIGOPTS/Brunel/TrigMuonRawEventFix.py
DaVinci is the fifth step in the MC production. In case of productions in
filtering mode a sixth DaVinci Phys WG is run. Here only the shared DaVinci
steps are described.
The version of DaVinci used for MC11a is v29r1
The DaVinci steps are set for the stripping and correspond to Stripping17
for 2011 data.
The steps depend on two different processing pass, respectively called
Stripping17NoPrescalingFlagged (without prescaling) and Stripping17Flagged (with prescaling).
In both cases the stripping is run in flagging mode.
The magnetic field polarity is chosen via the SIMCOND tags.
- 17904, Stripping17Flagged for MC11 MagDown, for MagDown, flag with prescale
Replaces:
- 15558 with older database tags
- 17903, Stripping17Flagged for MC11 MagUp, for MagUp, flag with prescale
Replaces:
- 15559 with older database tags
- 17902, Stripping17NoPrescalingFlagged for MC11 MagDown, for MagDown, flag w/o prescale
Replaces:
- 15578 with older database tags
- 17901, Stripping17NoPrescalingFlagged for MC11 MagUp, for MagDown, flag w/o prescale
Replaces:
- 15598 with older database tags
The options depend on the processing pass and for flagged with prescale (1 and 3) are:
- $APPCONFIGOPTS/DaVinci/DV-Stripping17-Stripping-MC.py
while for flagged without prescale (2) they are:
- $APPCONFIGOPTS/DaVinci/DV-Stripping17-Stripping-MC-NoPrescaling.py
Normally file of 100 to 200 events are produced
up to the fifth step, to keep the CPU time per job reasonable (12h to 24h) and
reduce the failure rate per job. For this reason the files are rather small, so
the last step in a production is to merge these smaller files into files of
~5 GB and reduce their number. These files are those registered in the
book-keeping.
The name of the processing pass is Merge12 and it is invisible in the
book-keeping path.
For productions where the additional filtering step will be run after the
common DaVinci stripping-flagged step the merging will be done as seventh step.
The merging step depends only on the input and output file format, as it is
independend of simulation conditions. The merging does so only for the DST and
nor for FSR at the moment.
The application used for the merging is LHCb v33r1.
The merging step when run as sixth step is:
- step 16018, Merge12 for MC11, for MagDown
The options are:
- $APPCONFIGOPTS/Merging/CopyDST.py
The input of the merging when run as sixth step is
allstream.dst (not
visible) and the output is
allstream.dst (visible)
For productions requiring to generate more than 10M events, a replacement
of the fifth step is
needed to reduce the amount of data kept on file and I/O access. For this
reason only interesting events must be selected and written out.
In this case one Phys WG will set up the specific step for one or few event
types. If event types are shared by various Phys WG, it is recommended they
combine their filtering.
It will also be needed to setup a specific merging step per filtering.
The application and options will be identical as for step 6a.
More information on what needs to be done is available on the
dedicated twiki page
This page was last edited on 2 Aug 2012 by
Gloria Corti
