|
|
Line 137: |
Line 137: |
| | O | | | O |
| | O | | | O |
− | | rowspan="5" | Defined in generator, [https://hallaweb.jlab.org/12GeV/Moller/doxygen/mollersim/html/d4/d3a/a00101_source.html MollerAnalysis.cc] and [https://hallaweb.jlab.org/12GeV/Moller/doxygen/mollersim/html/d3/d00/a00113_source.html MollerDetectorSD]?; value comes from generator? | + | | |
− | | rowspan="5" | Momentum directions at <b>vertex?</b> | + | | |
| |- | | |- |
| | px0 | | | px0 |
Line 144: |
Line 144: |
| | X | | | X |
| | X | | | X |
− | | + | | rowspan="4" | Defined in generator, [https://hallaweb.jlab.org/12GeV/Moller/doxygen/mollersim/html/d4/d3a/a00101_source.html MollerAnalysis.cc] and [https://hallaweb.jlab.org/12GeV/Moller/doxygen/mollersim/html/d3/d00/a00113_source.html MollerDetectorSD]?; value comes from generator? |
| + | | rowspan="4" | Momentum directions at <b>vertex?</b> |
| |- | | |- |
| | py0 | | | py0 |
Revision as of 16:09, 9 November 2012
Summary
The ROOT tree variables filled in MollerAnalysis.hh in AddData , which is called from MollerAnalysis.cc.
The values are defined all over the place!
I am trying to catalog exactly where, and decide whether they should be defined differently...
- x, y, z
- x0, y0, z0
- kineE, px, py, pz
- kineE0, px0, py0, pz0, theta0
- kineE1, px1, py1, pz1, theta1
- kineE2, px2, py2, pz2, theta2
- kineE_org, theta_org
- type, volume, event, ev_num, hit, track
- ion, process, creator
- diffXS, totXS, rate
List of variables
O - used for this generator
X - not used for this generator (seems to always be 0 or -1)
Variable
|
ee
|
ep
|
ine
|
Defined in...
|
Description
|
x
|
O
|
O
|
O
|
Defined in tracking; value comes from hit information
|
Positions at detector (mm)
|
y
|
O
|
O
|
O
|
z
|
O
|
O
|
O
|
x0
|
O
|
O
|
O
|
Set in generator; value comes from hit information
|
Positions at vertex (mm)
|
y0
|
O
|
O
|
O
|
z0
|
O
|
O
|
O
|
type
|
O
|
O
|
O
|
Defined in tracking; from hit information, but integer value defined in MollerDetectorSD
|
Particle number e- = 0 e+ = 1 p = 2 p = 3 photon = 4 all others = 5
|
volume
|
O
|
O
|
O
|
Defined in tracking; value comes from hit information
|
Volume number; needs work
|
rate
|
O
|
O
|
O
|
Defined in generator
|
Rate (Hz/μA), needs to be normalized to number thrown
|
track
|
O
|
O
|
O
|
Defined in tracking; value comes from hit information
|
Primaries are track = 1 (also 2, in case of mollers)
|
event
|
O
|
O
|
O
|
Defined in tracking GetEventID()
|
Currently the two moller tracks have the same event number
|
|
Variable
|
ee
|
ep
|
ine
|
Defined in...
|
Description
|
kineE
|
O
|
O
|
O
|
Defined in tracking; value comes from hit information
|
Momentum direction and energy (MeV) at detector
|
px
|
O
|
O
|
O
|
py
|
O
|
O
|
O
|
pz
|
O
|
O
|
O
|
kineE0
|
O
|
O
|
O
|
|
|
px0
|
X
|
X
|
X
|
Defined in generator, MollerAnalysis.cc and MollerDetectorSD?; value comes from generator?
|
Momentum directions at vertex?
|
py0
|
X
|
X
|
X
|
pz0
|
X
|
X
|
X
|
theta0
|
X
|
X
|
X
|
kineE1
|
O
|
O
|
O
|
|
Momentum directions at vertex?
|
px1
|
O
|
O
|
O
|
py1
|
O
|
O
|
O
|
pz1
|
O
|
O
|
O
|
theta1
|
O
|
O
|
O
|
kineE2
|
O
|
O
|
O
|
|
Momentum directions at vertex?
|
px2
|
O
|
O
|
O
|
py2
|
O
|
O
|
O
|
pz2
|
O
|
O
|
O
|
theta2
|
O
|
O
|
O
|
|
Variable
|
ee
|
ep
|
ine
|
Defined in...
|
Description
|
ion
|
X
|
O
|
O
|
Defined in MollerDetectorHit.hh; value comes from MollerDetectorSD - boolean?
|
|
ev_num
|
O
|
O
|
O
|
|
|
process
|
X
|
X
|
X
|
|
|
creator
|
O
|
O
|
O
|
|
|
hit
|
O
|
O
|
O
|
|
|
kineE_org
|
O
|
O
|
O
|
|
|
theta_org
|
O
|
O
|
O
|
|
|
diffXS
|
X
|
X
|
X
|
|
|
totXS
|
O
|
O
|
O
|
|
|
|
Notes
- For mollers, the number thrown is 2x the number specified; this will be changed in future versions...
- When secondaries are tracked, is second moller electron always track==2? Or are secondaries from first electron sometimes? Can we (should we) record secondaries from two moller electrons separately somehow?
Return to Simulation Projects
Return to MOLLER at 11 GeV E09-005