Version:
[ ReleaseNotes ] [ 1.0 ] [ 1.1 ] [ 2.0 ] [ 3.0 ] [ 3.1 ] [ 3.2 ] [ 4.0 ] [ 4.0.p1 ] [ 4.0.p2 ] [ 4.1 ] [ 4.1.p1 ] [ 5.0 ] [ 5.0.p1 ] [ 5.1 ] [ 5.1.p1 ] [ 5.2 ] [ 5.2.p1 ] [ 5.2.p2 ] [ 6.0 ] [ 6.0.p1 ] [ 6.1 ] [ 6.2 ] [ 6.2.p1 ] [ 6.2.p2 ] [ 7.0 ] [ 7.0.p1 ] [ 7.1 ] [ 7.1.p1 ] [ 8.0 ] [ 8.0.p1 ] [ 8.1 ] [ 8.1.p1 ] [ 8.1.p2 ] [ 8.2 ] [ 8.2.p1 ] [ 8.3 ] [ 8.3.p1 ] [ 8.3.p2 ] [ 9.0 ] [ 9.0.p1 ] [ 9.0.p2 ] [ 9.1 ] [ 9.1.p1 ] [ 9.1.p2 ] [ 9.1.p3 ] [ 9.2 ] [ 9.2.p1 ] [ 9.2.p2 ] [ 9.2.p3 ] [ 9.2.p4 ] [ 9.3 ] [ 9.3.p1 ] [ 9.3.p2 ] [ 9.4 ] [ 9.4.p1 ] [ 9.4.p2 ] [ 9.4.p3 ] [ 9.4.p4 ] [ 9.5 ] [ 9.5.p1 ] [ 9.5.p2 ] [ 9.6 ] [ 9.6.p1 ] [ 9.6.p2 ] [ 9.6.p3 ] [ 9.6.p4 ] [ 10.0 ] [ 10.0.p1 ] [ 10.0.p2 ] [ 10.0.p3 ] [ 10.0.p4 ] [ 10.1 ] [ 10.1.p1 ] [ 10.1.p2 ] [ 10.1.p3 ] [ 10.2 ] [ 10.2.p1 ] [ 10.2.p2 ] [ 10.2.p3 ] [ 10.3 ] [ 10.3.p1 ] [ 10.3.p2 ] [ 10.3.p3 ] [ 10.4 ] [ 10.4.p1 ] [ 10.4.p2 ] [ 10.4.p3 ] [ 10.5 ] [ 10.5.p1 ] [ 10.6 ] [ 10.6.p1 ] [ 10.6.p2 ] [ 10.6.p3 ] [ 10.7 ] [ 10.7.p1 ] [ 10.7.p2 ] [ 10.7.p3 ] [ 10.7.p4 ] [ 11.0 ] [ 11.0.p1 ] [ 11.0.p2 ] [ 11.0.p3, ] [ 11.0.p4 ] [ 11.1 ] [ 11.1.1 ] [ 11.1.2 ] [ 11.1.3 ] [ 11.2 ] [ 11.2.1 ] [ 11.2.2 ] [ 11.3.0 ]
1 =========================================================
2 Geant4 - an Object-Oriented Toolkit for Simulation in HEP
3 =========================================================
4
5
6 HADR02
7
8 Example and DMJET: V.Ivanchenko, A.Ivanchenko,
9 UrQMD: Kh Abdel-Waged et al, A. Dotti
10 CRMC: A. Ribon (with contributions by T. Pierog and A. Tykhonov)
11 CERN, Geneva, Switzerland
12 Geant4 Associate International
13 University of Bordeaux, CENBG/IN2P3/CNRS
14 (ESA contract 22712/09/NL/AT)
15
16
17 This example application is providing simulation of ion beam interaction with different
18 targets. Hadronic aspects of beam target interaction are demonstrated in the example
19 including longitudinal profile of energy deposition, spectra of secondary particles,
20 isotope production spectra. The results are presenting in a form of average numbers
21 and histograms. All ion/ion models of Geant4 are available.
22
23 In addition an interface to the FORTRAN code UrQMD-1.3rc developed by Kh, Abdel-Waged et al
24 for the KACST/NCMP. UrQMD model by S.A.Bass et al. Prog.Part.Nucl.Phys. 41 (1998) 225
25 and M.Bleicher et al. J.Phys. G25 (1999) 1859.
26 UrQMD can be used only for ion-ion physics or for all hadronic inelastic interactions.
27
28 The interface to the Cosmic Ray Monte Carlo (CRMC) allows to use generators -
29 such as EPOS, DPMJET, SIBYLL etc. - for hadron-nucleus and nucleus-nucleus collisions
30 at very high energies.
31
32 INSTALLATION
33
34 For simulation with Geant4 native models installation procedure is the same as for
35 other examples.
36
37 HOW TO RUN
38
39 To run the example:
40
41 Hadr02 <yourmacro> QGSP_BIC
42
43 The last parameter is optional. It is the name of Geant4 reference Physics List,
44 alternatively Physics List can be defined via environment variable
45
46 setenv PHYSLIST QGSP_BIC
47
48 ACTIVATION OF URQMD INTERFACE
49
50 UrQMD 1.3 FORTRAN code is NOT provided with Geant4 code-base.
51 You can get UrQMD code from UrQMD code website: http://urqmd.org
52 The Geant4 interface has been developed and tested against urqmd-1.3cr
53 Once the tarball urqmd-1.3cr.tar.gz has been downloaded copy it in the
54 urqmd1_3 directory of this example.
55 To compile support for UrQMD interface in the example define the environment
56 variable G4_USE_URQMD. i.e. by typing:
57
58 setenv G4_USE_URQMD 1
59
60 Two possible uses of UrQMD interface are possible: use UrQMD code only for
61 ion-ion interactions or use the provided UrQMD physics list (all hadron inelastic interactions
62 use UrQMD).
63 To run the example with UrQMD only for ion-ion physics:
64
65 Hadr02 urqmd.in QGSP_BIC
66
67 The last parameter is optional. It is the name of Geant4 reference Physics List on
68 top of which a new ion physics is added. Alternatively Physics List can be defined via
69 environment variable
70
71 setenv PHYSLIST QGSP_BIC
72
73 To run the example with the full UrQMD physics:
74
75 Hadr02 default.in UrQMD
76 or:
77 setenv PHYSLIST UrQMD
78 Hadr02 default.in
79
80 UrQMD physics list can be used in any application, releavant headers and source files (*UrQDM*)
81 should be copied in your application source tree, together with the urqmd1_3 sub-directory.
82 Your application makefile should also be modified following the example of the makefile for this
83 example.
84
85 ACTIVATION OF CRMC INTERFACE
86
87 The CRMC (Cosmic Ray Monte Carlo) interface is NOT provided with Geant4 code-base.
88 A modified version of the CRMC interface for Geant4 applications has been kindly
89 prepared by Tanguy Pierog (IKP) and Andrii Tykhonov (Universite' de Geneve)
90 and can be obtained here:
91 https://gitlab.ikp.kit.edu/AirShowerPhysics/crmc/-/tree/svn/geant4
92
93 Assuming that this special version of CRMC is installed in the subdirectory
94 crmc-svn-geant4/ , you need first to build it : please look at the README and
95 README_GEANT4_CRMC_INTERFACE files for detailed instructions on how to build it.
96 In short:
97
98 1. Install BOOST
99 2. Install HepMC (and define the corresponding environmental variable HEP_ROOT)
100 3. Install FASTJET (and define the corresponding environmental variable
101 FASTJET_ROOT_DIR)
102 4. Set the LD_LIBRARY_PATH as follows:
103 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${HEP_ROOT}/lib:${FASTJET_ROOT_DIR}/lib
104 5. Source the Geant4 script geant4make.sh , e.g.
105 source /your-geant4-installation-dir/share/Geant4-10.7.1/geant4make/geant4make.sh
106 6. cd crmc-svn-geant4/
107 7. mkdir Build/ ; cd Build/ # Subdirectory where to build and install CRMC
108 8. cmake ../
109 9. make
110 10. make install # Yes, you need also to install it (in the same directory)!
111
112 After you have built CRMC you can build the Hadr02 application that uses it as follows:
113
114 1. Define the following environmental variable (in addition to the environmental
115 variables defined above, needed to build CRMC):
116 export G4_USE_CRMC=1
117 export CRMCROOT=/your-crmc-installation-dir/crmc-svn-geant4/
118 export CPATH=${CPATH}:${CRMCROOT}/Build/src:${CRMCROOT}/src
119 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CRMCROOT}/Build/lib
120 export CRMC_CONFIG_FILE=${CRMCROOT}/Build/crmc.param
121 2. cd /your-geant4/examples/extended/hadronic/Hadr02
122 3. mkdir Build/ ; cd Build/ # Subdirectory where to build Hadr02
123 4. cmake -DG4_USE_CRMC=ON -DGeant4_DIR=/your-geant4-installation-dir/ ../
124 5. make
125
126 To run the application:
127
128 1. Define the following environmental variable (besides the previous ones):
129 export PHYSLIST=CRMC_FTFP_BERT
130 2. cd /your-geant4/examples/extended/hadronic/Hadr02/Build
131 3. ./Hadr02 crmc.in
132
133 which runs the special "CRMC_FTFP_BERT" physics list, defined in this example,
134 which consists of using the standard FTFP_BERT physics list for hadrons of
135 kinetic energies below 100 GeV, while using CRMC above 110 GeV : in the interval
136 between 100 and 110 GeV, there is the transition between FTFP and CRMC (which
137 means that one of these two models is randomly chosen for each interaction,
138 with a probability which is 100% (0%) for FTFP (CRMC) at 100 GeV, and
139 decreases (grows) linearly to 0% (100%) for FTFP (CRMC) at 110 GeV.
140 Which of the MC generators of CRMC is actually used is specified in the file:
141 include/G4CRMCModel.hh
142 (search for string "***LOOKHERE***" : these are the available choices:
143 EPOS LHC (0) - the default - , EPOS 1.99 (1), SIBYLL 2.3c (6), and
144 DPMJET 3 (12) ).
145
146 Notice that we use CRMC only for inelastic final-state of pion- , kaon- ,
147 proton- , neutron- and ion-nuclear interactions, whereas for the rest
148 (i.e. elastic and inelastic cross sections, elastic final-state interactions,
149 hyperon- , antihyperon- , antinucleon- and light anti-ion nuclear interactions)
150 we use Geant4 FTFP_BERT.
151
152 GEOMETRY
153
154 The Target volume is a cylinder placed inside Check cylindrical volume. The
155 Check volume is placed inside the World volume. The radius and the length of
156 the Check volume are 1 mm larger than the radius and the length of the Target.
157 The material of the Check volume is the same as the World material. The World
158 volume has the sizes 10 mm larger than that of the Target volume. Any material
159 from the Geant4 database can be defined. The default World material is
160 G4Galactic and the default Target material is aluminum. The Target is
161 subdivided on number of equal slices. Following UI commands are available to
162 modify the geometry:
163
164 /testhadr/TargetMat G4_Pb
165 /testhadr/WorldMat G4_AIR
166 /testhadr/TargetRadius 10 mm
167 /testhadr/TargetLength 20 cm
168 /testhadr/NumberDivZ 200
169
170 Beam direction coincides with the target axis and is Z axis in the global
171 coordinate system. G4ParticleGun is used as a primary generator. The energy
172 and the type of the beam can be defined via standard UI commands
173
174 /gun/energy 150 GeV
175 /gun/particle ion
176 /gun/ion 6 12
177
178 Default beam position is -(targetHalfLength + 5*mm) and direction along Z axis.
179 Beam position and direction can be changed by gun UI commands:
180
181 /gun/position 1 10 3 mm
182 /gun/direction 1 0 0
183
184 however, position command is active only if before it the flag is set
185
186 /testhadr/DefaultBeamPosition false
187
188 SCORING
189
190 The scoring is performed with the help of UserStackingAction class and a
191 sensitive detector class associated with a target slice.
192 Each secondary particle is scored by the StackingAction. In
193 the StackingAction it is also possible to kill all or only EM (e+, e-, gamma)
194 secondary particles
195
196 /testhadr/killAll
197 /testhadr/KillEM
198
199 To control running the following options are available:
200
201 /run/printProgress 10
202
203
204 PHYSICS
205
206 PhysicsList of the application uses components, which are distributed with
207 Geant4 in /geant4/physics_lists subdirectory.
208
209 Reference Physics Lists are used and the environment variable PHYSLIST should
210 be defined.
211
212 Additionally it is possible to add ion-ion interactions using UI command
213
214 /testhadr/ionPhysics HIJING
215 /testhadr/ionPhysics QrQMD
216
217
218 VISUALIZATION
219
220 For interactive mode G4 visualization options and variables should be
221 defined, then the example should be recompiled:
222
223 gmake visclean
224 gmake
225
226 The vis.mac file can be used an example of visualization. The following command can
227 be used:
228
229 /testhadr/DrawTracks charged
230 /testhadr/DrawTracks charged+n
231 /testhadr/DrawTracks neutral
232 /testhadr/DrawTracks all
233
234
235 HISTOGRAMS
236
237 All histograms are normalized to the number of events.
238
