lars/geant4
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Import Geant4 11.0.0 source tree

Browse Source
This commit is contained in:
Gabriele Cosmo
2021-12-12 17:16:06 +01:00
parent 80e2389dd8
commit 84f33a068c
593 changed files with 68589 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
examples/extended/hadronic/Hadr02/.README.txt
+231
View File
@@ -0,0 +1,231 @@
///\file "hadronic/Hadr02/.README.txt"
///\brief Example Hadr02 README page
/*! \page ExampleHadr02 Example Hadr02
Example and DMJET:
\author V.Ivanchenko, A.Ivanchenko, \n
UrQMD: Kh Abdel-Waged et al, A. Dotti \n
CERN, Geneva, Switzerland \n
Geant4 Associate International \n
University of Bordeaux, CENBG/IN2P3/CNRS \n
(ESA contract 22712/09/NL/AT)
This example application is providing simulation of ion beam interaction with different
targets. Hadronic aspects of beam target interaction are demonstrated in the example
including longitudinal profile of energy deposition, spectra of secondary particles,
isotope production spectra. The results are presenting in a form of average numbers
and histograms. All ion/ion models of Geant4 are available and also the interface to
the FORTRAN code DPMJET-2.5 developed by J.Ranft for FLUKA. The interface was developed
by P.Truscott (QinetiQ, UK) under European Space Agency (ESA) contract 19770/06/NL/JD.
In addition an interface to the FORTRAN code UrQMD-1.3rc developed by Kh, Abdel-Waged et al
for the KACST/NCMP. UrQMD model by S.A.Bass et al. Prog.Part.Nucl.Phys. 41 (1998) 225
and M.Bleicher et al. J.Phys. G25 (1999) 1859.
UrQMD can be used only for ion-ion physics or for all hadronic inelastic interactions.
\section Hadr02_s1 INSTALLATION
For simulation with Geant4 native models installation procedure is the same as for
other examples.
\subsection Hadr02_sub_s11 ACTIVATION OF DPMJET INTERFACE
In order to use DPMJET additional installation steps are required.
It is recommended to use DPMJET with SLC5 64 bit PC with gcc4.3.2 or newer compiler.
Two environment variables should be defined:
\verbatim
G4DPMJET2_5DATA - path to Glauber data
CERNLIB - path to cernlib library
G4_USE_DPMJET - flag of DPMJET activation
\endverbatim
To run the example with DPMJET:
\verbatim
Hadr02 dpmjet.in QGSP_BIC
\endverbatim
The last parameter is optional. It is the name of Geant4 reference Physics List on
top of which a new ion physics is added. Alternatively Physics List can be defined via
environment variable
\verbatim
setenv PHYSLIST QGSP_BIC
\endverbatim
\subsection Hadr02__sub_s12 ACTIVATION OF URQMD INTERFACE
UrQMD 1.3 FORTRAN code is NOT provided with Geant4 code-base.
You can get UrQMD code from UrQMD code website: http://urqmd.org
The Geant4 interface has been developed and tested against urqmd-1.3cr
Once the tarball urqmd-1.3cr.tar.gz has been downloaded copy it in the
urqmd1_3 directory of this example.
To compile support for UrQMD interface in the example define the environment
variable G4_USE_URQMD. i.e. by typing:
\verbatim
setenv G4_USE_URQMD 1
\endverbatim
Two possible uses of UrQMD interface are possible: use UrQMD code only for
ion-ion interactions or use the provided UrQMD physics list (all hadron inelastic interactions
use UrQMD).
To run the example with UrQMD only for ion-ion physics:
\verbatim
Hadr02 urqmd.in QGSP_BIC
\endverbatim
The last parameter is optional. It is the name of Geant4 reference Physics List on
top of which a new ion physics is added. Alternatively Physics List can be defined via
environment variable
\verbatim
setenv PHYSLIST QGSP_BIC
\endverbatim
To run the example with the full UrQMD physics:
\verbatim
Hadr02 default.in UrQMD
\endverbatim
or:
\verbatim
setenv PHYSLIST UrQMD
Hadr02 default.in
\endverbatim
UrQMD physics list can be used in any application, releavant headers and source files (*UrQDM*)
should be copied in your application source tree, together with the urqmd1_3 sub-directory.
Your application makefile should also be modified following the example of the makefile for this
example.
\section Hadr02_s2 GEOMETRY
The Target volume is a cylinder placed inside Check cylindrical volume. The
Check volume is placed inside the World volume. The radius and the length of
the Check volume are 1 mm larger than the radius and the length of the Target.
The material of the Check volume is the same as the World material. The World
volume has the sizes 10 mm larger than that of the Target volume. Any material
from the Geant4 database can be defined. The default World material is
G4Galactic and the default Target material is aluminum. The Target is
subdivided on number of equal slices. Following UI commands are available to
modify the geometry:
\verbatim
/testhadr/TargetMat G4_Pb
/testhadr/WorldMat G4_AIR
/testhadr/TargetRadius 10 mm
/testhadr/TargetLength 20 cm
/testhadr/NumberDivZ 200
\endverbatim
Beam direction coincides with the target axis and is Z axis in the global
coordinate system. G4ParticleGun is used as a primary generator. The energy
and the type of the beam can be defined via standard UI commands
\verbatim
/gun/energy 150 GeV
/gun/particle ion
/gun/ion 6 12
\endverbatim
Default beam position is -(targetHalfLength + 5*mm) and direction along Z axis.
Beam position and direction can be changed by gun UI commands:
\verbatim
/gun/position 1 10 3 mm
/gun/direction 1 0 0
\endverbatim
however, position command is active only if before it the flag is set
\verbatim
/testhadr/DefaultBeamPosition false
\endverbatim
\section Hadr02_s3 SCORING
The scoring is performed with the help of UserStackingAction class and a
sensitive detector class associated with a target slice.
Each secondary particle is scored by the StackingAction. In
the StackingAction it is also possible to kill all or only EM (e+, e-, gamma)
secondary particles
\verbatim
/testhadr/killAll
/testhadr/KillEM
\endverbatim
To control running the following options are available:
\verbatim
/run/printProgress 10
\endverbatim
\section Hadr02_s4 PHYSICS
PhysicsList of the application uses components, which are distributed with
Geant4 in /geant4/physics_lists subdirectory.
Reference Physics Lists are used and the environment variable PHYSLIST should
be defined.
Additionally it is possible to add ion-ion interactions using UI command
\verbatim
/testhadr/ionPhysics DPMJET
/testhadr/ionPhysics FTF
\endverbatim
\section Hadr02_s5 VISUALIZATION
For interactive mode G4 visualization options and variables should be
defined, then the example should be recompiled:
\verbatim
gmake visclean
gmake
\endverbatim
The vis.mac file can be used an example of visualization. The following command can
be used:
\verbatim
/testhadr/DrawTracks charged
/testhadr/DrawTracks charged+n
/testhadr/DrawTracks neutral
/testhadr/DrawTracks all
\endverbatim
\section Hadr02_s6 HISTOGRAMS
It is possible to choose the format of the output file with
histograms using UI command:
\verbatim
/testhadr/HistoName name
/testhadr/HistoType type
\endverbatim
The following types are available: root, xml(aida). They will be
stored in the file "name.root", or "name.xml".
If the environment variable HISTODIR is defined, files are stored in this
subdirectory.
To show the content of a histogram ID=i the commands may be applied:
\verbatim
/testhadr/HistoPrint i
\endverbatim
All histograms are normalized to the number of events.
*/
examples/extended/hadronic/Hadr02/README
+238
View File
@@ -0,0 +1,238 @@
=========================================================
Geant4 - an Object-Oriented Toolkit for Simulation in HEP
=========================================================
HADR02
Example and DMJET: V.Ivanchenko, A.Ivanchenko,
UrQMD: Kh Abdel-Waged et al, A. Dotti
CRMC: A. Ribon (with contributions by T. Pierog and A. Tykhonov)
CERN, Geneva, Switzerland
Geant4 Associate International
University of Bordeaux, CENBG/IN2P3/CNRS
(ESA contract 22712/09/NL/AT)
This example application is providing simulation of ion beam interaction with different
targets. Hadronic aspects of beam target interaction are demonstrated in the example
including longitudinal profile of energy deposition, spectra of secondary particles,
isotope production spectra. The results are presenting in a form of average numbers
and histograms. All ion/ion models of Geant4 are available.
In addition an interface to the FORTRAN code UrQMD-1.3rc developed by Kh, Abdel-Waged et al
for the KACST/NCMP. UrQMD model by S.A.Bass et al. Prog.Part.Nucl.Phys. 41 (1998) 225
and M.Bleicher et al. J.Phys. G25 (1999) 1859.
UrQMD can be used only for ion-ion physics or for all hadronic inelastic interactions.
The interface to the Cosmic Ray Monte Carlo (CRMC) allows to use generators -
such as EPOS, DPMJET, SIBYLL etc. - for hadron-nucleus and nucleus-nucleus collisions
at very high energies.
INSTALLATION
For simulation with Geant4 native models installation procedure is the same as for
other examples.
HOW TO RUN
To run the example:
Hadr02 <yourmacro> QGSP_BIC
The last parameter is optional. It is the name of Geant4 reference Physics List,
alternatively Physics List can be defined via environment variable
setenv PHYSLIST QGSP_BIC
ACTIVATION OF URQMD INTERFACE
UrQMD 1.3 FORTRAN code is NOT provided with Geant4 code-base.
You can get UrQMD code from UrQMD code website: http://urqmd.org
The Geant4 interface has been developed and tested against urqmd-1.3cr
Once the tarball urqmd-1.3cr.tar.gz has been downloaded copy it in the
urqmd1_3 directory of this example.
To compile support for UrQMD interface in the example define the environment
variable G4_USE_URQMD. i.e. by typing:
setenv G4_USE_URQMD 1
Two possible uses of UrQMD interface are possible: use UrQMD code only for
ion-ion interactions or use the provided UrQMD physics list (all hadron inelastic interactions
use UrQMD).
To run the example with UrQMD only for ion-ion physics:
Hadr02 urqmd.in QGSP_BIC
The last parameter is optional. It is the name of Geant4 reference Physics List on
top of which a new ion physics is added. Alternatively Physics List can be defined via
environment variable
setenv PHYSLIST QGSP_BIC
To run the example with the full UrQMD physics:
Hadr02 default.in UrQMD
or:
setenv PHYSLIST UrQMD
Hadr02 default.in
UrQMD physics list can be used in any application, releavant headers and source files (*UrQDM*)
should be copied in your application source tree, together with the urqmd1_3 sub-directory.
Your application makefile should also be modified following the example of the makefile for this
example.
ACTIVATION OF CRMC INTERFACE
The CRMC (Cosmic Ray Monte Carlo) interface is NOT provided with Geant4 code-base.
A modified version of the CRMC interface for Geant4 applications has been kindly
prepared by Tanguy Pierog (IKP) and Andrii Tykhonov (Universite' de Geneve)
and can be obtained here:
https://gitlab.ikp.kit.edu/AirShowerPhysics/crmc/-/tree/svn/geant4
Assuming that this special version of CRMC is installed in the subdirectory
crmc-svn-geant4/ , you need first to build it : please look at the README and
README_GEANT4_CRMC_INTERFACE files for detailed instructions on how to build it.
In short:
1. Install BOOST
2. Install HepMC (and define the corresponding environmental variable HEP_ROOT)
3. Install FASTJET (and define the corresponding environmental variable
FASTJET_ROOT_DIR)
4. Set the LD_LIBRARY_PATH as follows:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${HEP_ROOT}/lib:${FASTJET_ROOT_DIR}/lib
5. Source the Geant4 script geant4make.sh , e.g.
source /your-geant4-installation-dir/share/Geant4-10.7.1/geant4make/geant4make.sh
6. cd crmc-svn-geant4/
7. mkdir Build/ ; cd Build/ # Subdirectory where to build and install CRMC
8. cmake ../
9. make
10. make install # Yes, you need also to install it (in the same directory)!
After you have built CRMC you can build the Hadr02 application that uses it as follows:
1. Define the following environmental variable (in addition to the environmental
variables defined above, needed to build CRMC):
export G4_USE_CRMC=1
export CRMCROOT=/your-crmc-installation-dir/crmc-svn-geant4/
export CPATH=${CPATH}:${CRMCROOT}/Build/src:${CRMCROOT}/src
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CRMCROOT}/Build/lib
export CRMC_CONFIG_FILE=${CRMCROOT}/Build/crmc.param
2. cd /your-geant4/examples/extended/hadronic/Hadr02
3. mkdir Build/ ; cd Build/ # Subdirectory where to build Hadr02
4. cmake -DG4_USE_CRMC=ON -DGeant4_DIR=/your-geant4-installation-dir/ ../
5. make
To run the application:
1. Define the following environmental variable (besides the previous ones):
export PHYSLIST=CRMC_FTFP_BERT
2. cd /your-geant4/examples/extended/hadronic/Hadr02/Build
3. ./Hadr02 crmc.in
which runs the special "CRMC_FTFP_BERT" physics list, defined in this example,
which consists of using the standard FTFP_BERT physics list for hadrons of
kinetic energies below 100 GeV, while using CRMC above 110 GeV : in the interval
between 100 and 110 GeV, there is the transition between FTFP and CRMC (which
means that one of these two models is randomly chosen for each interaction,
with a probability which is 100% (0%) for FTFP (CRMC) at 100 GeV, and
decreases (grows) linearly to 0% (100%) for FTFP (CRMC) at 110 GeV.
Which of the MC generators of CRMC is actually used is specified in the file:
include/G4CRMCModel.hh
(search for string "***LOOKHERE***" : these are the available choices:
EPOS LHC (0) - the default - , EPOS 1.99 (1), SIBYLL 2.3c (6), and
DPMJET 3 (12) ).
Notice that we use CRMC only for inelastic final-state of pion- , kaon- ,
proton- , neutron- and ion-nuclear interactions, whereas for the rest
(i.e. elastic and inelastic cross sections, elastic final-state interactions,
hyperon- , antihyperon- , antinucleon- and light anti-ion nuclear interactions)
we use Geant4 FTFP_BERT.
GEOMETRY
The Target volume is a cylinder placed inside Check cylindrical volume. The
Check volume is placed inside the World volume. The radius and the length of
the Check volume are 1 mm larger than the radius and the length of the Target.
The material of the Check volume is the same as the World material. The World
volume has the sizes 10 mm larger than that of the Target volume. Any material
from the Geant4 database can be defined. The default World material is
G4Galactic and the default Target material is aluminum. The Target is
subdivided on number of equal slices. Following UI commands are available to
modify the geometry:
/testhadr/TargetMat G4_Pb
/testhadr/WorldMat G4_AIR
/testhadr/TargetRadius 10 mm
/testhadr/TargetLength 20 cm
/testhadr/NumberDivZ 200
Beam direction coincides with the target axis and is Z axis in the global
coordinate system. G4ParticleGun is used as a primary generator. The energy
and the type of the beam can be defined via standard UI commands
/gun/energy 150 GeV
/gun/particle ion
/gun/ion 6 12
Default beam position is -(targetHalfLength + 5*mm) and direction along Z axis.
Beam position and direction can be changed by gun UI commands:
/gun/position 1 10 3 mm
/gun/direction 1 0 0
however, position command is active only if before it the flag is set
/testhadr/DefaultBeamPosition false
SCORING
The scoring is performed with the help of UserStackingAction class and a
sensitive detector class associated with a target slice.
Each secondary particle is scored by the StackingAction. In
the StackingAction it is also possible to kill all or only EM (e+, e-, gamma)
secondary particles
/testhadr/killAll
/testhadr/KillEM
To control running the following options are available:
/run/printProgress 10
PHYSICS
PhysicsList of the application uses components, which are distributed with
Geant4 in /geant4/physics_lists subdirectory.
Reference Physics Lists are used and the environment variable PHYSLIST should
be defined.
Additionally it is possible to add ion-ion interactions using UI command
/testhadr/ionPhysics HIJING
/testhadr/ionPhysics QrQMD
VISUALIZATION
For interactive mode G4 visualization options and variables should be
defined, then the example should be recompiled:
gmake visclean
gmake
The vis.mac file can be used an example of visualization. The following command can
be used:
/testhadr/DrawTracks charged
/testhadr/DrawTracks charged+n
/testhadr/DrawTracks neutral
/testhadr/DrawTracks all
HISTOGRAMS
All histograms are normalized to the number of events.
examples/extended/hadronic/Hadr02/hijing1_383/README
+118
View File
@@ -0,0 +1,118 @@
HIJING interface
----------------
Khaled Abdel-Waged
--------------------
version 0.0, 1-11-2012
----------------------
>Installation requirements
--------------------------
The Geant4 interface to HIJING uses the following software tools and packages:
1. HIJING (available at fttp://nta0.lbl.gov/pub/xnwang/hijing)
2. The following Geant4 versions:
− ver.9.5 or above
The interface and original HIJING code have been compiled and tested using:
• gcc 4.1.2 with gfortran (FORTRAN95) and GNUmake)
Operating systems used for this test is:
Red Hat Linux 4.1.2-64
>Changes in the Fortran code
----------------------------
1) The main subroutines
SUBROUTINE HIJSET(EFRM, FRAME, PROJ, TARG, IAP, IZP, IAT, IZT)
is replaced with
SUBROUTINE HIJSET(EFRM)
SUBROUTINE HIJING (FRAME, BMIN, BMAX)
is replaced with
SUBROUTINE HIJING (BMIN, BMAX)
The input variables are directly inserted into the following common block:
COMMON/HIPARNT/HIPR1(100),IHPR2(50),HINT1(100),IHNT2(50)
Projectile:
IHNT2(1)=IAP // Nucleus mass number
or IHNT2(1)=1 //Hadron
IHNT2(2)=IZP //charge
IHNT2(5)=0 //id code
Target:
IHNT2(3)=IAT
IHNT2(4)=IZT
IHNT2(6)=0 //id Target (Fixed)
Rest Mass:
HINT1(8)= //projectile
HINT1(9)= //Target
2) In subroutines HIJSET and HIJING,
Since Geant4 hadronic cascade models always works in the LABoratory frame
the statement Frame=”LAB” is inserted.
3)Random number generator
The two random generator functions become one!
This is done by replacing
RAN(NSEED) with RLU(0) in hijing1.383.f
>Consequences of conversion from f77 (g77) to gfortran
------------------------------------------------------
When running HIJING code in gfortran directly, the execution is blocked.
This problem is solved by the following changes
1) You have to add in the GNUmake file, the line
FFLAGS=-fno-automatic
This treats each program unit as if the SAVE statement were specified
for every local variable and array referenced in it.
2) Problem related to the function ROMG(x) in hijing1.383.f:
FUNCTION ROMG(X)
C This gives the eikonal function from a table
C calculated in the first call
DIMENSION FR(0:1000)
DATA I0/0/
COMMON/EIKONAL/FR !New->Khaled
IF(I0.NE.0) GO TO 100
DO 50 I=1,1001
XR=(I-1)*0.01
FR(I-1)=OMG0(XR)
50 CONTINUE
100 I0=1
IF(X.GE.10.0) THEN
ROMG=0.0
RETURN
ENDIF
IX=INT(X*100)
ROMG=(FR(IX)*((IX+1)*0.01-X)+FR(IX+1)*(X-IX*0.01))/0.01
RETURN
END
Our analysis shows that the array FR() is not saved in the subsequent calls of the function ROMG().
Therefore, the statement “COMMON/EIKONAL/FR” is inserted, as shown above.
>Interface design
-----------------
The use of HIJING physics in Geant4 has resulted in the introduction of a new event model (G4HIJING_Model).
The G4HIJING_Model class is derived from G4HadronicInteraction, and is defined within the Geant4 user physics
list if access to HIJING physics is required. It controls initialisation of HIJING through common block variables.