This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
gauss:gauss [2012/03/29 16:00] – decianm | gauss:gauss [2012/04/05 11:59] – [How to write out MCParticles in Gauss] che | ||
---|---|---|---|
Line 14: | Line 14: | ||
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, | ||
+ | |||
+ | To avoid error messages like: | ||
+ | |||
+ | MainEventGaussSim | ||
+ | |||
+ | you have to make sure that you have included | ||
+ | <code python> | ||
+ | Gauss().Phases = [" | ||
+ | Gauss().Output = ' | ||
+ | Gauss().Histograms = ' | ||
+ | </ | ||
+ | in your Gauss-Job.py file. | ||
===== Running EvtGen standalone ===== | ===== Running EvtGen standalone ===== | ||
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> | ||
+ | #Event Type: 11114001 | ||
from Configurables import Generation | from Configurables import Generation | ||
Generation().EventType = 11114001 | Generation().EventType = 11114001 | ||
Line 33: | Line 46: | ||
Generation().StandAloneDecayTool.SignalPIDList = [ 511,-511 ] | Generation().StandAloneDecayTool.SignalPIDList = [ 511,-511 ] | ||
</ | </ | ||
+ | |||
+ | These both things (running EvtGen standalone and writing out MCParticles) can of course be combined. |