gauss:gauss
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| gauss:gauss [2011/10/29 15:22] – decianm | gauss:gauss [2012/04/10 16:16] (current) – 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 ===== | ||
| + | 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. | ||
| + | |||
| + | ===== Running Particle Gun ===== | ||
| + | If you want to run a particle gun producing a particle type which should decay in EvtGen you have to change your options file accordingly to this prototype file (Gauss v41r1): | ||
| + | <code python> | ||
| + | # file / | ||
| + | # | ||
| + | # Event Type: 27876001 | ||
| + | # | ||
| + | # ASCII decay Descriptor: { [ D*+ -> pi+ pi+ pi- ]cc } | ||
| + | # | ||
| + | from Configurables import ParticleGun | ||
| + | from Configurables import MomentumRange | ||
| + | ParticleGun().addTool( MomentumRange ) | ||
| + | from GaudiKernel import SystemOfUnits | ||
| + | ParticleGun().MomentumRange.MomentumMin = 150.0*SystemOfUnits.GeV | ||
| + | from GaudiKernel import SystemOfUnits | ||
| + | ParticleGun().MomentumRange.MomentumMax = 1000.0*SystemOfUnits.GeV | ||
| + | ParticleGun().EventType = 27876001 | ||
| + | ParticleGun().ParticleGunTool = " | ||
| + | ParticleGun().NumberOfParticlesTool = " | ||
| + | ParticleGun().MomentumRange.PdgCodes = [ 413,-413 ] | ||
| + | |||
| + | from Configurables import ToolSvc | ||
| + | from Configurables import EvtGenDecay | ||
| + | ToolSvc().addTool( EvtGenDecay ) | ||
| + | ToolSvc().EvtGenDecay.UserDecayFile = " | ||
| + | from Gaudi.Configuration import * | ||
| + | importOptions( " | ||
| + | ParticleGun().DecayTool = " | ||
| + | </ | ||
| + | |||
| + | The numbering is incorrect as options file for Particle Guns start with 5. As the numbering scheme in case of Particle Guns aims at stable particles the official numbering scheme does not make much sense in this case. Anyhow, the numbering does not affect the performance of the option file for Particle Guns. | ||
| + | In addition you have to add the line | ||
| + | <code python> | ||
| + | Gauss().Production = ' | ||
| + | </ | ||
| + | to your Gauss Job file. | ||
gauss/gauss.1319894556.txt.gz · Last modified: 2011/10/29 15:22 by decianm
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
