Back to home page

EIC code displayed by LXR

 
 

    


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

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