SCT parametric simulation - Revision history

Razuvaev: /* SctParSim */

2021-11-24T06:34:37Z

‎SctParSim

Razuvaev: /* How to run */

2021-11-24T05:16:38Z

‎How to run

Razuvaev at 10:10, 22 November 2021

2021-11-22T10:10:09Z

Razuvaev: /* Configure example */

2021-11-22T10:08:33Z

‎Configure example

Razuvaev: /* Configure example */

2021-11-22T09:04:49Z

‎Configure example

Razuvaev: /* Podio output */

2021-11-22T09:03:09Z

‎Podio output

Razuvaev: /* Podio input */

2021-11-22T09:02:47Z

‎Podio input

Razuvaev: /* Analysis */

2021-11-22T09:00:33Z

‎Analysis

Razuvaev: /* SctParSim */

2021-11-22T08:42:29Z

‎SctParSim

Razuvaev: /* EvtGen */

2021-11-22T08:37:40Z

‎EvtGen

@@ Line 140: / Line 140: @@
 </pre>
-The full parameters list is [https://ctd.inp.nsk.su/wiki/index.php/Parametric_simulation here].
+The full parameters list is [https://ctd.inp.nsk.su/wiki/index.php/SctParSim_(Aurora) here].
 == Analysis ==

@@ Line 10: / Line 10: @@
 cd run
 cp /home/razuvaev/public/misc/pi_ms_f1_mppc2_px3_d200_mla4_graph2d.root .
 cp /home/razuvaev/public/misc/g4beamline_pi_plus_100k_parse.root .
 cp /home/razuvaev/public/misc/g4beamline_mu_plus_100k_parse.root .

← Older revision		Revision as of 10:10, 22 November 2021
Line 1:		Line 1:
		+	= How to run =
		+
		+	Login to stark or proxima machine.
		+	<pre>
		+	ssh stark -X
		+	setupSCTAU; asetup SCTauSim,master,latest
		+	mkdir workarea
		+	cd workarea
		+	mkdir run
		+	cd run
		+	cp /home/razuvaev/public/misc/pi_ms_f1_mppc2_px3_d200_mla4_graph2d.root .
		+	cp /home/razuvaev/public/misc/gun1.cfg .
		+	cp /home/razuvaev/public/misc/g4beamline_pi_plus_100k_parse.root .
		+	cp /home/razuvaev/public/misc/g4beamline_mu_plus_100k_parse.root .
		+	ctaurun SctParSimAlg/sctparsim_test_particle_gun.py
		+	</pre>
		+
	= Configure example =		= Configure example =

@@ Line 1: / Line 1: @@
 = Configure example =
-There is an example of running the entire chain from generating particles to running an analysis tool. A more detailed description of the algorithms and their parameters is presented below.
+There are some examples to run the parametric simulation
+{| class="wikitable"
-<pre>
+|-
-from Configurables import ApplicationMgr
+! Using tools
+! Link
-from Gaudi.Configuration import *
+|-
-from Configurables import GenAlg, EvtGenInterface
+| Read from a ROOT-file, write to a ROOT-file
-from Configurables import HepMCToEDMConverter
+| [https://git.inp.nsk.su/sctau/aurora/-/blob/master/Simulation/SctParSimAlg/jobOptions/sctparsim_test_read.py sctparsim_test_read.py]
-from Configurables import ScTauDataSvc
+|-
+| Generate using the particle gun, write to a ROOT-file
-from Configurables import Gaudi__ParticlePropertySvc
+| [https://git.inp.nsk.su/sctau/aurora/-/blob/master/Simulation/SctParSimAlg/jobOptions/sctparsim_test_particle_gun.py sctparsim_test_particle_gun.py]
-from PathResolver import PathResolver
+|-
+| Generate using <code>EvtGen</code>, write to a ROOT-file
-############################
+| [https://git.inp.nsk.su/sctau/aurora/-/blob/master/Simulation/SctParSimAlg/jobOptions/sctparsim_test_evtgen.py sctparsim_test_evtgen.py]
-####  Event generation  ####
+|-
-############################
+| Generate using <code>EvtGen</code>, use the analysis tool
-podioevent = ScTauDataSvc("EventDataSvc")
+| [https://git.inp.nsk.su/sctau/aurora/-/blob/master/Simulation/SctParSimAlg/jobOptions/sct_run_test_analisis.py sct_run_test_analisis.py]
+|}
-# Particle service
-particlePropertySvc = Gaudi__ParticlePropertySvc(
-    "ParticlePropertySvc",
-    ParticlePropertiesFile=PathResolver.FindDataFile('GenParticleData/ParticleTable.txt')
-−
-−
-# EvtGen
-evtgen = EvtGenInterface('SignalProvider')
-#evtgen.userdec = "./mydec.dec"
-#evtgen.rootParticle = "J/psi"
-−
-gen = GenAlg('EvtGenAlg', SignalProvider=evtgen)
-gen.hepmc.Path = 'hepmc'
-−
-# HepMC3 to PODIO
-edm = HepMCToEDMConverter("Converter")
-edm.hepmc.Path=gen.hepmc.Path
-edm.genparticles.Path="allGenParticles"
-edm.genvertices.Path="allGenVertices"
-−
-############################
-# SctParSim
-############################
-from Configurables import SctParSimAlg
-−
-sct_alg = SctParSimAlg('SctAlg')
-#sct_alg.CaloSystemTool.caloClSizeEGamma = 0.2 # Example how to change a subsystem parameter
-−
-############################
-# Podio output
-############################
-out = PodioOutput('out', filename=ofile)
-out.outputCommands = ["keep *"]
-−
-############################
-# Analisis
-############################
-from Configurables import EventLoader
-from Configurables import NtupleAlg, NTupleSvc
-from Configurables import ParticleCombinerAlg
-−
-evlo = EventLoader('EvtLoader')
-evlo.pcl.Path = 'Particles' # Branch (in the input ROOT-file) for reading
-evlo.pListMap.Path = 'Lists1'
-evlo.plists = [['gamma']] # Partilce list for further analisis
-−
-# Select particle combinations
-cmbr = ParticleCombinerAlg('Cmbr',
-    decStr = 'pi0 -> gamma gamma', # Investigated decay
-    cutStr = 'E > 0.5', # Selection criteria
-    selfConj = True # if neutral particle True, else False
-−
-−
-cmbr.pListMapI = evlo.pListMap.Path
-cmbr.pListMapO.Path = 'Lists2'
-−
-# Select variables to save to n-tuple
-tupl = NtupleAlg('piTuple')
-tupl.listName = 'pi0'
-tupl.fileName = 'scttuple/tup'
-−
-# List contains the particle parametes to write an output file
-tupl.vars = [['px_mc', 'py_mc', 'pz_mc', 'E', 'pi0 -> ^gamma ^gamma'],
-    ['M', ''],
-−
-−
-tupl.pListMapI.Path = cmbr.pListMapO.Path
-NTupleSvc(Output = ["scttuple DATAFILE='tup.root' OPT='NEW' TYP='ROOT'"])
-−
-−
-############################
-# Running algorithms
-############################
-−
-options= {
-    'TopAlg' : [gen, edm, sct_alg, evlo, cmbr, tupl, out],
-    'EvtSel' : 'NONE',
-    'ExtSvc' : [particlePropertySvc, podioevent],
-    'EvtMax' : 10000,
-    'StatusCodeCheck' : True,
-    'AuditAlgorithms' : True,
-    'AuditTools'      : True,
-    'AuditServices'   : True,
-    'OutputLevel'     : INFO,
-    'HistogramPersistency' : 'ROOT',
-−
-−
-ApplicationMgr(**options)
-</pre>
 == Event generation ==

← Older revision		Revision as of 09:04, 22 November 2021
Line 248:		Line 248:

	The reading algorithm has the parameter: filename - an output file name.		The reading algorithm has the parameter: filename - an output file name.
		+
		+	== Running algorithm ==
		+
		+	Some necessary parametrs to run the algorithms:
		+	* TopAlg - a list of the using algorithms
		+	* EvtMax - a number of events

← Older revision		Revision as of 09:03, 22 November 2021
Line 233:		Line 233:

	== Podio output ==		== Podio output ==
		+
		+	It is possible to write the particle parameters to a ROOT file.
		+
		+	You have to import the library
		+	<pre>
		+	from Configurables import PodioOutput
		+	</pre>
		+
		+	and to create the algorithm instance
		+	<pre>
		+	out = PodioOutput('out', filename=ofile)
		+	out.outputCommands = ["keep *"]
		+	</pre>
		+
		+	The reading algorithm has the parameter: filename - an output file name.

@@ Line 128: / Line 128: @@
 </pre>
-The reading algorithm has the following parametres:
+The reading algorithm has the following parameters:
 * input - an input file name
 * collections - a name of a branch with MC particles

← Older revision		Revision as of 09:00, 22 November 2021
Line 216:		Line 216:

	== Analysis ==		== Analysis ==
		+
		+	The analysis tool has the following parameters:
		+	* EventLoader
		+	** pcl.Path - a branch (in the input ROOT-file) for reading
		+	** plists - a partilce list for further analisis. if it is necessary to consider not only positive, but also negative particles, the label "сс" is used. For example <code>[['K+ cc'], ['pi+ cc']]</code>. Also it is possible to write a kinematic constraint; for example <code>[['K+ cc', 'p > 0.5'], ['pi+ cc']]</code> (kaons don't have the momentum less then 0.5 GeV)
		+
		+	* ParticleCombinerAlg
		+	** decStr - an investigated decay
		+	** cutStr - a selection criteria
		+	** selfConj - if neutral particle <code>True</code>, else <code>False</code>
		+
		+	* NtupleAlg
		+	** vars - a list contains the particle parameters to write an output file. A particle in the decay string can be selected using the "^" symbol. If a decay isn't written (<code>''</code>), the information about parameters will be about a parent particle.
		+
		+	More information about the analysis tool is [https://ctd.inp.nsk.su/wiki/index.php/Use_Analysis_package here].
		+
	== Podio output ==		== Podio output ==

@@ Line 201: / Line 201: @@
 == SctParSim ==
 == Analysis ==
 == Podio output ==

@@ Line 190: / Line 190: @@
 More information about EvtGen is [https://ctd.inp.nsk.su/wiki/index.php/Event_generators here].
-<code>EvtGen</code> function has the following parameters:
+<code>EvtGen</code> interface has the following parameters:
 * <code>dec</code> - EvtGen users decay file. It can be one of the included in Aurora files or absolute path to your own decay file. Inclusive MC generation does not require user decay file
 * <code>root</code> - root particle for EvtGen. <code>vpho</code> (virtual photon) should be used for non-resonant processes