User Tools

Site Tools


gauss:gauss

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
gauss:gauss [2012/03/29 16:00] decianmgauss: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, i.e. only tools which only access 4-vectors will run...) The root file can then be run over with an MCTupleTool in DaVinci (with certain restrictions, i.e. only tools which only access 4-vectors will run...)
 +
 +To avoid error messages like: 
 +
 +MainEventGaussSim         FATAL SimInit:: Exception throw: put():: could not register 'LHCb::MCHeader' at address '/Event/MC/Header' StatusCode=2
 +
 +you have to make sure that you have included
 +<code python>
 +Gauss().Phases = ["Generator"]
 +Gauss().Output = 'NONE'
 +Gauss().Histograms = 'NONE'
 +</code>
 +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 ]
 </code> </code>
 +
 +These both things (running EvtGen standalone and writing out MCParticles) can of course be combined.
gauss/gauss.txt · Last modified: 2012/04/10 16:16 by che