This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
gauss:gauss [2011/10/29 15:22] – created decianm | gauss:gauss [2012/04/05 11:59] – [How to write out MCParticles in Gauss] che | ||
---|---|---|---|
Line 2: | Line 2: | ||
===== How to write out MCParticles in Gauss ===== | ===== How to write out MCParticles in Gauss ===== | ||
It can be very useful to let Gauss write out MCParticles in the Generation directly (without the detector simulation), | It can be very useful to let Gauss write out MCParticles in the Generation directly (without the detector simulation), | ||
- | This can be achieved the following way: | + | This can be achieved the following way (write this at the end of your version of Gauss-Job.py): |
<code python> | <code python> | ||
gtos = GenerationToSimulation() | gtos = GenerationToSimulation() | ||
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, | ||
+ | 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 ===== | ||
+ | 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 (Gauss v41r1): | ||
+ | <code python> | ||
+ | #Event Type: 11114001 | ||
+ | from Configurables import Generation | ||
+ | Generation().EventType = 11114001 | ||
+ | from Configurables import StandAloneDecayTool | ||
+ | Generation().SampleGenerationTool = " | ||
+ | Generation().addTool( StandAloneDecayTool ) | ||
+ | Generation().StandAloneDecayTool.ProductionTool = " | ||
+ | |||
+ | from Configurables import ToolSvc | ||
+ | from Configurables import EvtGenDecay | ||
+ | |||
+ | ToolSvc().addTool( EvtGenDecay ) | ||
+ | ToolSvc().EvtGenDecay.UserDecayFile =" | ||
+ | Generation().StandAloneDecayTool.SignalPIDList = [ 511,-511 ] | ||
+ | </ | ||
+ | |||
+ | These both things (running EvtGen standalone and writing out MCParticles) can of course be combined. |