struct munhits

Contains PISA (GEANT) hits data from muon identifier system
float tof
time (ns) of hit relative to interaction
float de
total energy loss (GeV) of particle inside volume
float rhit[3]
position (cm) of hit in PHENIX global coordinates
float phit[3]
momentum (GeV/c) of particle
long track_num
GEANT track number of particle
short trk_id
GEANT id of particle
short plane_num
plane_num = 1000*arm + gap (arm=1 for South, =2 for North; gap [1,6])
short itrsub
not used (mMuiGhitFilter refers to it)
short itrksub
not used (mMuiGhitFilter refers to it)

Documentation

Contains PISA (GEANT) hits data from muon identifier system.

If I am reading the sources correctly (pisa/src/mum/mua_gustep.f), the position and time are those at which the particle *enters* the detector volume (inwvol = 1).

In PHOOL, munhits is a wrapped STAF-style table provided for convenience and backwards-compatibility; its data is copied from a PISAEvent object. Might it be preferable to use PISAEvent directly in the MuID software and to eliminate munhits?

float tof
time (ns) of hit relative to interaction

float de
total energy loss (GeV) of particle inside volume

float rhit[3]
position (cm) of hit in PHENIX global coordinates

float phit[3]
momentum (GeV/c) of particle

long track_num
GEANT track number of particle

short trk_id
GEANT id of particle

short plane_num
plane_num = 1000*arm + gap (arm=1 for South, =2 for North; gap [1,6])

short itrsub
not used (mMuiGhitFilter refers to it)

short itrksub
not used (mMuiGhitFilter refers to it)

alphabetic index hierarchy of classes

this page has been generated automatically by doc++

(c)opyright by Malte Zöckler, Roland Wunderling
contact: doc++@zib.de