This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
gauss:gauss [2012/03/29 15:59] – decianm | gauss:gauss [2012/03/29 16:01] – decianm | ||
---|---|---|---|
Line 15: | Line 15: | ||
The root file can then be run over with an MCTupleTool in DaVinci (with certain restrictions, | The root file can then be run over with an MCTupleTool in DaVinci (with certain restrictions, | ||
- | ===== How to write only run EvtGen ===== | + | ===== Running |
You can run EvtGen standalone, letting the particles decay at rest. This is very fast, as no underlying event has to be generated. | You can run EvtGen standalone, letting the particles decay at rest. This is very fast, as no underlying event has to be generated. | ||
- | A prototype file could look like: | + | A prototype file could look like (Gauss v41r1): |
<code python> | <code python> | ||
from Configurables import Generation | from Configurables import Generation | ||
Line 32: | Line 32: | ||
ToolSvc().EvtGenDecay.UserDecayFile =" | ToolSvc().EvtGenDecay.UserDecayFile =" | ||
Generation().StandAloneDecayTool.SignalPIDList = [ 511,-511 ] | Generation().StandAloneDecayTool.SignalPIDList = [ 511,-511 ] | ||
- | < | + | </code> |
+ | |||
+ | These both things (running EvtGen standalone and writing out MCParticles) can of course be combined. |