| Geant4 Cross Reference |
>> 1 $Id: README,v 1.1 2006/05/09 16:22:19 maire Exp $
1 ---------------------------------------------- 2 -------------------------------------------------------------------
2 3
3 ========================================= 4 =========================================================
4 Geant4 - an Object-Oriented Toolkit for S 5 Geant4 - an Object-Oriented Toolkit for Simulation in HEP
5 ========================================= 6 =========================================================
6 << 7
7 TestEm17 8 TestEm17
8 -------- 9 --------
9 This example is intended to check impl 10 This example is intended to check implementation of the processes
10 of muon interactions: ionization, dire << 11 of muon interactions: ionization, direct (e+,e-) production,
11 pair production, bremsstrahlung, and mu-nucl << 12 bremsstrahlung, mu-nuclear interaction.
12 It allows to compute differential cross sect 13 It allows to compute differential cross sections (as function of the
13 energy transfered to secondaries), total cro << 14 energy tranfered to secondaries), total cross sections and to compare
14 with analytic calculations. 15 with analytic calculations.
15 16
16 1- GEOMETRY DEFINITION 17 1- GEOMETRY DEFINITION
17 18
18 It is a single box of homogeneous medium. 19 It is a single box of homogeneous medium.
19 Two parameters define the geometry : 20 Two parameters define the geometry :
20 - the material of the box, 21 - the material of the box,
21 - the (full) size of the box. 22 - the (full) size of the box.
22 23
23 The default geometry (1 m of Iron) is constr 24 The default geometry (1 m of Iron) is constructed in
24 DetectorConstruction, but the above paramete 25 DetectorConstruction, but the above parameters can be changed
25 interactively via the commands defined in De 26 interactively via the commands defined in DetectorMessenger.
26 27
27 2- PHYSICS LIST 28 2- PHYSICS LIST
28 29
29 The Physics List of the example uses the mai << 30 The physics list contains only electromagnetic processes for muon,
30 (builder) called "local", which includ << 31 adding G4MuNuclearInteraction and seting of upper energy range limit
31 processes under study. As an alternati << 32 to 1000 PeV).
32 and "emstandard_opt4" constructors may << 33
33 << 34 Standard (default) and g4v52 (frozen at the release Geant4 v.5.2)
34 Default energy range for EM processes << 35 physics can be choosen.
35 is from 100*eV to 1000*PeV. <<
36 <<
37 Optionally "muNucl" builder may be add <<
38 inelastic interaction. <<
39 36
40 3- AN EVENT : THE PRIMARY GENERATOR 37 3- AN EVENT : THE PRIMARY GENERATOR
41 38
42 The primary kinematic consists of a single p 39 The primary kinematic consists of a single particle starting at the edge
43 of the box. The type of the particle and its 40 of the box. The type of the particle and its energy are set in
44 PrimaryGeneratorAction (mu+ 10 TeV), and can 41 PrimaryGeneratorAction (mu+ 10 TeV), and can be changed via the G4
45 build-in commands of ParticleGun class (see 42 build-in commands of ParticleGun class (see the macros provided with
46 this example). 43 this example).
47 44
48 4- PHYSICS 45 4- PHYSICS
49 46
50 The incident particle is a muon. During the 47 The incident particle is a muon. During the tracking, secondary
51 particles are killed. 48 particles are killed.
52 49
53 The number of interactions are plotted as a 50 The number of interactions are plotted as a function of the energy
54 transfered to the secondaries. 51 transfered to the secondaries.
55 The total number of interactions is recorded << 52 The total number of interactions is recorded, and the total crossSection
56 section computed from this. << 53 computed from this.
57 54
58 At RunAction::EndOfRun(..), the above << 55 At EndOfRun, the above results are compared with analytic calculations.
59 calculations. The functions computing << 56 The functions which compute the theoritical crossSections have been
60 provided by the G4 MEPhI group, and implemen << 57 provided by the G4 MEPhI group, and grouped in MuCrossSection class.
61 58
62 5- HISTOGRAMS 59 5- HISTOGRAMS
63 60
64 The test contains built-in 1D histograms for << 61 The test contains 4 built-in 1D histograms, which are managed by the
65 Monte Carlo simulation, which are mana << 62 HistoManager class and its Messenger.
66 and its Messenger: <<
67 63
68 1 Relative muon transferred energy dis << 64 1 Monte-Carlo relative transferred energy distribution histo
69 (log10(eps/Emu kin) for knock-on e 65 (log10(eps/Emu kin) for knock-on electrons (ionization)
70 2 -"- direct (e+,e-) pair production << 66 2 -"- direct (e+,e-) pair production
71 3 -"- bremsstrahlung by muons << 67 3 -"- bremsstrahlung
72 4 -"- nuclear interaction by muons << 68 4 -"- nuclear interaction
73 5 ionistion for hadrons << 69
74 6 (e+,e-) pair production by hadrons <<
75 7 bremsstrahlung by hadrons <<
76 8 direct mu+,mu- pair production by muons <<
77 <<
78 The histos can be activated individually wit 70 The histos can be activated individually with the command :
79 /testem/histo/setHisto id nbBins valMin val << 71 /testem/histo/setHisto id nbBins valMin valMax : min and max values of
80 min and max values of log10(eps/Emu << 72 log10(eps/Emu kin).
81 73
82 At EndOfRun the corresponding histos for ana 74 At EndOfRun the corresponding histos for analytic calculations are
83 automatically created and filled (histo 11 t << 75 automatically created anf filled (histo 6 to 9), and the comparison
>> 76 (G4 divided by theory) is done in histos 11 to 14.
84 77
85 One can control the name and the type of the 78 One can control the name and the type of the histograms file with
86 the command: << 79 the commands:
87 /testem/histo/setFileName name (default te 80 /testem/histo/setFileName name (default testem17)
88 << 81 /testem/histo/setFileType name (default hbook)
>> 82
>> 83 Note that, by default, histograms are disabled. To activate them,
>> 84 uncomment the flag G4ANALYSIS_USE in GNUmakefile.
>> 85
89 6- VISUALIZATION 86 6- VISUALIZATION
90 87
91 The Visualization Manager is set in the main 88 The Visualization Manager is set in the main().
92 The initialisation of the drawing is done vi 89 The initialisation of the drawing is done via the commands
93 /vis/... in the macro vis.mac. To get visual 90 /vis/... in the macro vis.mac. To get visualisation:
94 > /control/execute vis.mac 91 > /control/execute vis.mac
95 92
96 The detector has a default view which is a l 93 The detector has a default view which is a longitudinal view of the
97 box. 94 box.
98 95
99 The tracks are drawn at the end of event, an 96 The tracks are drawn at the end of event, and erased at the end of run.
100 97
101 7- HOW TO START ? 98 7- HOW TO START ?
102 99
>> 100 compile and link to generate an executable
>> 101 % cd geant4/examples/extended/electromagnetic/TestEm17
>> 102 % gmake
>> 103
103 execute TestEm17 in 'batch' mode from macro 104 execute TestEm17 in 'batch' mode from macro files :
104 % TestEm17 allproc.mac 105 % TestEm17 allproc.mac
105 106
106 execute TestEm17 in 'interactive mode' with 107 execute TestEm17 in 'interactive mode' with visualization :
107 % TestEm17 108 % TestEm17
108 Idle> control/execute vis.mac 109 Idle> control/execute vis.mac
109 .... 110 ....
110 Idle> type your commands 111 Idle> type your commands
111 .... 112 ....
112 Idle> exit 113 Idle> exit
>> 114
>> 115 8- USING HISTOGRAMS
>> 116
>> 117 By default the histograms are not activated. To activate histograms
>> 118 the environment variable G4ANALYSIS_USE should be defined. For instance
>> 119 uncomment the flag G4ANALYSIS_USE in GNUmakefile.
>> 120
>> 121 Before compilation of the example it is optimal to clean up old files:
>> 122 gmake histclean
>> 123 gmake
>> 124
>> 125 To use histograms, at least one of the AIDA implementations should be
>> 126 available (see http://aida.freehep.org).
>> 127
>> 128 8a - PI
>> 129
>> 130 A package including AIDA and extended interfaces also using Python is PI,
>> 131 available from: http://cern.ch/pi
>> 132
>> 133 Once installed PI or PI-Lite in a specified local area $MYPY, it is required
>> 134 to add the installation path to $PATH, i.e. for example, for release 1.2.1 of
>> 135 PI:
>> 136 setenv PATH ${PATH}:$MYPI/1.2.1/app/releases/PI/PI_1_2_1/rh73_gcc32/bin
>> 137
>> 138 CERN users can use the PATH to the LCG area on AFS.
>> 139 Before running the example the command should be issued:
>> 140 eval `aida-config --runtime csh`
>> 141
>> 142 8b - OpenScientist
>> 143
>> 144 OpenScientist is available at http://OpenScientist.lal.in2p3.fr.
>> 145
>> 146 You have to "setup" the OpenScientist AIDA implementation before compiling
>> 147 (then with G4ANALYSIS_USE set) and running your Geant4 application.
>> 148
>> 149 On UNIX you setup, with a csh flavoured shell :
>> 150 csh> source <<OpenScientist install path>/aida-setup.csh
>> 151 or with a sh flavoured shell :
>> 152 sh> . <<OpenScientist install path>/aida-setup.sh
>> 153 On Windows :
>> 154 DOS> call <<OpenScientist install path>/aida-setup.bat
>> 155
>> 156 You can use various file formats for writing (AIDA-XML, hbook, root).
>> 157 These formats are readable by the Lab onx interactive program
>> 158 or the OpenPAW application. See the web pages.
>> 159
>> 160
>> 161 With OpenPAW, on a run.hbook file, one can view the histograms
>> 162 with something like :
>> 163 OS> opaw
>> 164 opaw> h/file 1 run.hbook ( or opaw> h/file 1 run.aida or run.root)
>> 165 opaw> zone 2 2
>> 166 opaw> h/plot 1
>> 167 opaw> h/plot 2