Back to home page

EIC code displayed by LXR

 
 

    


Warning, /geant4/examples/extended/runAndEvent/RE01/README.md is written in an unsupported language. File is not indexed.

0001 \page ExampleRE01 Example RE01
0002 
0003 
0004  Contact : M.Asai (SLAC) 
0005 
0006 ## Introduction
0007 
0008  This example demonstrates how to connect the information between
0009 primary particles and hits. It also utilize some user-information
0010 classes.
0011 
0012 ### Geometry and region information
0013 
0014  It has a quite simple cylindrical tracker of 5 layers and a
0015 cylindrical calorimeter of lead and scintillator. Dedicated regions
0016 are assigned to both tracker and calorimeter mother volumes not
0017 for setting additional production thresholds but for adding some
0018 more information to these regions. RE01RegionInformation is the
0019 class for this purpose.
0020  A "readout geometry" is attached to the calorimeter to define
0021 its cells.
0022 
0023 ### Physics
0024 
0025  This example basically uses QGSP_BERT physics list. In addition 
0026 to this, G4UnknownDecayPhysics is used for adding decay process to
0027 G4UnknownParticle.
0028 
0029 ### Event generator
0030 
0031  An event sample is attached. This event has a Higgs particle
0032 which decays into e+e- and mu+mu- pairs through two Z bosons.
0033 It uses G4HEPEvtInterface. 
0034  In this example, by utilizing G4UnknownParticle, all particles
0035 appear in the primary event are converted to G4Track and then
0036 to RE01Trajectory. Relation between primary particles and track
0037 IDs are shown at the end of event execution.
0038 
0039 ## "Source track" information
0040 
0041  "Source track" is meant for a track that is either a primary
0042 particle or a track born is the tracking region. This information
0043 is stored in RE01TrackInformation class object and copied from
0044 a parent track to its daughters.
0045 
0046 ### Track suspension
0047 
0048  All source tracks are suspended for their tracking when they are
0049 getting into the calorimeter region. Thus, all tracks in the tracker
0050 region are tracked before generating any shower in the calorimeter.
0051 
0052 ### Tracker hits associated with primary particle information
0053 
0054  Information kept in RE01TrackInformation is used to connect each
0055 tracker hit to the primary particle.
0056 
0057 ### Energy deposition of each source track
0058 
0059  Utilizing RE01StackingAction, shower generation is done for each
0060 souorce track separately, and thus energy deposition in calorimeter
0061 cells are shown for each individual source track. With the trajectory
0062 information, energy deposition for each primary particle can also
0063 be gotten.
0064