Moller sim dictionary
From Hall A Wiki
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)
|
|
|
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?
- Vertex momenta are set in generators, then again in MollerAnalysis (to zero?) and then in MollerDetectorSD... but I think it should only be set in generator. The SD definition is what sets the momentum2 for the elastic eps and inelastics to the vertexMomentum, which is from track info (fTrack->GetVertexMomentumDirection()). Momentum0 is the "pre-vertex" momentum (all in z direction) in all cases.
- kineE is defined as a double in MollerDetectorSD as fTrack->GetKineticEnergy(), but the tree variable is aHit->GetKineticEnergy. kineE0 is defined in MollerDetectorSD as GetVertexKineticEnergy(), then in MollerSteppingVerbose as thePrePoint->GetKineticEnergy(), and in MollerAnalysis as fTrack->GetVertexKineticEnergy(). kineE2 is set to kineE0 in SD.
Return to Simulation Projects
Return to MOLLER at 11 GeV E09-005