|
|
Geant4 is a toolkit for the simulation of the passage of particles through matter develop by the Geant4 team. It is used in LHCb through a GEANT4 project built with CMT and released in Geant4_release_area.
Geant4 v80r0 (geant4.8.0) doxygen documentation, release.notes, requirements, distribution kit
Geant4 v71r0 (geant4.7.1) doxygen documentation, release.notes, requirements, distribution kit
Geant4 v70r0p1 (geant4.7.0.p01) doxygen documentation, release notes, requirements, distribution kit
Geant4 v61r0 (geant4.6.1) was used for the DC04 production by Gauss v15r* doxygen documentation, release notes, requirements, distribution kit
There is one package per global library with the name of the global library.
There is a
G4config to fix the geant4 version, the geant4 path and the location of
include files, libraries and data files:
G4_native_version
G4VERS v<i>r<j>
G4PATH /afs/cern.ch/sw/geant4/releases
G4SHARE
$G4PATH/$G4_native_version
G4SRC
$G4SHARE/source
G4INSTALL
$Geant4_release_area/GEANT4/GEANT4_$G4VERS/InstallArea
G4LIB
$G4INSTALL/$BINDIR/lib
G4INCLUDE $G4INSTALL/include
G4LIB is appended to LD_LIBRARY_PATH
GaudiPolicy is used from $Gaudi_release_area to get compiler options,
tags and patterns definitions.
CLHEP is used from $Gaudi_release_area
Geant4 data files are accessed from $LHCb_release_area/PARAM/Geant4Files/v<n>r<m>
which sets G4LEVELGAMMADATA
Packages do not contain any source files nor include files.
Include files are copied from the geant4 release area include/ directory to
the InstallArea of the project version the first time a "source setup.csh" is
performed in the Geant4Sys package.
> cd Geant4Sys/v52r4/cmt
> source setup.csh
>cd ../../..; ls *
InstallArea/include
Source files are copied from the geant4 release area to the local package the
first time a "source setup.csh" is performed in the package:
> cd G4geometry/v4r0/cmt
> source setup.csh
> cd ..; ls
cmt doc management solids biasing divisions magneticfield navigation volumes
When some source files of a package need to be modified they are kept in
srcnew/ directory and compiled after all other files to replace original ones.
srcnew/ directory is kept on a CVS branch of the package.
Softlinks are made to all dynamic libraries in the InstallArea of the
project version.