source: trunk/examples/extended/runAndEvent/RE01/README @ 1345

Last change on this file since 1345 was 807, checked in by garnier, 16 years ago

update

File size: 2.2 KB
Line 
1
2 RE01 - An extended example for run and event
3 --------------------------------------------
4
5 Contact : M.Asai (SLAC)
6
71. Introduction
8
9 This example demonstrates how to connect the information between
10primary particles and hits. It also utilize some user-information
11classes.
12
131.1 Geometry and region information
14
15 It has a quite simple sylindrical tracker of 5 layers and a
16sylindrical calorimeter of lead and scintillator. Dedicated regions
17are assigned to both tracker and calorimeter mother volumes not
18for setting additional production thresholds but for adding some
19more information to these regions. RE01RegionInformation is the
20class for this purpose.
21 A "readout geometry" is attached to the calorimeter to define
22its cells.
23
241.2 Physics
25
26 This example basically uses LHEP_BERT physics list. In addition
27to this, RE01DecayPhysics is used for adding G4UnknownParticle and
28G4UnknownDecay process.
29
301.3 Event generator
31
32 An event sample is attached. This event has a Higgs particle
33which decays into e+e- and mu+mu- pairs through two Z bosons.
34It uses G4HEPEvtInterface.
35 In this example, by utilizing G4UnknownParticle, all particles
36appear in the primary event are converted to G4Track and then
37to RE01Trajectory. Relation between primary particles and track
38IDs are shown at the end of event execution.
39
402. "Source track" information
41
42 "Source track" is meant for a track that is either a primary
43particle or a track born is the tracking region. This information
44is stored in RE01TrackInformation class object and copied from
45a parent track to its daughters.
46
472.1 Track suspension
48
49 All source tracks are suspended for their tracking when they are
50getting into the calorimeter region. Thus, all tracks in the tracker
51region are tracked before generating any shower in the calorimeter.
52
532.2 Tracker hits associated with primary particle information
54
55 Information kept in RE01TrackInformation is used to connect each
56tracker hit to the primary particle.
57
582.3 Energy deposition of each source track
59
60 Utilizing RE01StackingAction, shower generation is done for each
61souorce track separately, and thus energy deposition in calorimeter
62cells are shown for each individual source track. With the trajectory
63information, energy deposition for each primary particle can also
64be gotten.
65
66
Note: See TracBrowser for help on using the repository browser.