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
Next revisionBoth sides next revision
gauss:gauss [2011/10/29 15:22] decianmgauss:gauss [2012/03/29 16:02] decianm
Line 15: Line 15:
 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...)
  
 +===== 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 = "StandAloneDecayTool";
 +Generation().addTool( StandAloneDecayTool )
 +Generation().StandAloneDecayTool.ProductionTool = "PythiaProduction";
 +
 +from Configurables import ToolSvc
 +from Configurables import EvtGenDecay
 +
 +ToolSvc().addTool( EvtGenDecay )
 +ToolSvc().EvtGenDecay.UserDecayFile ="$DECFILESROOT/dkfiles/Bd_Kstmumu=DecProdCut.dec"
 +Generation().StandAloneDecayTool.SignalPIDList = [ 511,-511 ]
 +</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