What are the two pieces of software
required for building Geant4?
Selecting an Example
Application
Building an Example
Application
Single versus
Multi-User Installation
What are the two pieces of software required
for building Geant4?
gcc 3.2.3 or 3.4.5:
gcc is the compiler that is recommended for Geant4 on Linux. Users have also had success with gcc 4.1.1. You will not have success with earlier versions of gcc.
To check your version, type: gcc –v.
CLHEP:
CLHEP is a set of base libraries that have long provided great functionality for the particle physics community. They provide things like matrix manipulations and four-vector tools. The Geant4 collaboration has chosen to use these libraries rather than re-invent these wheels. Please note that while CLHEP and Geant4 both come out of the particle physics communities, they are separate products - the Geant4 collaboration is not responsible for maintenance, distribution or documentation of CLHEP.
Getting and Installing CLHEP
Go to the CLHEP source download page:
http://proj-clhep.web.cern.ch/proj-clhep/DISTRIBUTION/clhep.html
From the "Source" section near the bottom of the page, select "clhep-2.0.3.1.tgz"
which corresponds to:
http://proj-clhep.web.cern.ch/proj-clhep/DISTRIBUTION/distributions/clhep-2.0.3.1.tgz
The file is about 5MB.
Put it into your directory of choice, such as:
~/CLHEP
Navigate to this directory and unpack the file:
cd ~/CLHEP
tar -zxvf clhep-2.0.3.1.tgz
The unpacking process will begin, starting with:
2.0.3.1/
2.0.3.1/CLHEP/
2.0.3.1/CLHEP/CVS/
2.0.3.1/CLHEP/CVS/Root
2.0.3.1/CLHEP/CVS/Repository
And ending with:
2.0.3.1/CLHEP/install-sh
2.0.3.1/CLHEP/config.guess
2.0.3.1/CLHEP/config.sub
2.0.3.1/CLHEP/Makefile.in
2.0.3.1/CLHEP/configure
For the following step, note that there are two dashes in a row before the word "prefix".
Also note that for this command you should use the absolute path for your CLHEP, such as:
/u/ey/perl/CLHEP
rather than a relative path, such as:
~/CLHEP
And be sure to point to your top level CLHEP directory, NOT:
/u/ey/perl/CLHEP/2.0.3.1/CLHEP
Now navigate into the unpacked directory and begin the
configuration process.
Of course, substitute your actual CLHEP path here:
cd 2.0.3.1/CLHEP
./configure --prefix /u/ey/perl/CLHEP
You should get a response that starts with:
checking
build system type... i686-pc-linux-gnu
checking
host system type... i686-pc-linux-gnu
checking
target system type... i686-pc-linux-gnu
checking
for a BSD-compatible install... /usr/bin/install -c
checking
whether build environment is sane... yes
And ends with:
config.status:
creating test/exctest4.sh
config.status:
creating test/exctestNothrow.sh
config.status:
creating test/excDblThrow.sh
config.status:
creating Exceptions/defs.h
config.status:
executing depfiles commands
The complete output from the above command can be found in this same web directory as:
Run the build process:
make
You should get a response that starts with:
Making
all in Units
make[1]:
Entering directory `/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP/Units'
Making
all in Units
make[2]:
Entering directory
`/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP/Units/Units'
make all-am
And ends with:
make[1]:
Entering directory `/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP'
./build-clheplib
Units Vector Evaluator GenericFunctions Geometry Random Matrix RandomObjects
RefCount Cast Exceptions
rm
-f libCLHEP-2.0.3.1.a
liblist=`./getObjectList
-static Units Vector Evaluator GenericFunctions Geometry Random Matrix
RandomObjects RefCount Cast Exceptions`; \
ar
cru libCLHEP-2.0.3.1.a $liblist; ranlib libCLHEP-2.0.3.1.a
rm
-f libCLHEP-2.0.3.1.so
liblist=`./getObjectList
-shared Units Vector Evaluator GenericFunctions Geometry Random Matrix
RandomObjects RefCount Cast Exceptions`; \
g++
-O -ansi -pedantic -Wall -D_GNU_SOURCE -g -O2 -o libCLHEP-2.0.3.1.so -shared
-Wl,-soname,libCLHEP-2.0.3.1.so $liblist -o libCLHEP-2.0.3.1.so
make[1]:
Leaving directory `/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP'
The complete output from the above command can be found in this same web directory as:
Finally, move the build products to their installation area:
make install
You should get a response that starts with:
Making
install in Units
make[1]:
Entering directory `/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP/Units'
Making
install in Units
make[2]:
Entering directory
`/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP/Units/Units'
And ends with:
test
-z "/afs/slac.stanford.edu/u/ey/perl/CLHEP/lib" || mkdir -p --
"/afs/slac.stanford.edu/u/ey/perl/CLHEP/lib"
/usr/bin/install -c -m 644
'libCLHEP-2.0.3.1.a'
'/afs/slac.stanford.edu/u/ey/perl/CLHEP/lib/libCLHEP-2.0.3.1.a'
ranlib
'/afs/slac.stanford.edu/u/ey/perl/CLHEP/lib/libCLHEP-2.0.3.1.a'
/usr/bin/install -c
'libCLHEP-2.0.3.1.so' '/afs/slac.stanford.edu/u/ey/perl/CLHEP/lib/libCLHEP-2.0.3.1.so'
make[2]:
Nothing to be done for `install-data-am'.
make[2]:
Leaving directory `/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP'
make[1]:
Leaving directory `/afs/slac.stanford.edu/u/ey/perl/CLHEP/2.0.3.1/CLHEP'
The complete output from the above command can be found in this same web directory as:
You will now have directories such as:
~/CLHEP/include
and
~/CLHEP/lib
You're done setting up CLHEP.
Much more detailed instructions on installation of CLHEP are available from the CLHEP web site:
http://proj-clhep.web.cern.ch/proj-clhep/INSTALLATION/newCLHEP-install.html
Getting Geant4
From the top of the Geant4 home page:
http://geant4.web.cern.ch/geant4/
Select "Download" from near the top right corner of the page.
Select "Unix tar format, compressed using gzip"
which corresponds to:
http://geant4.web.cern.ch/geant4/support/source/geant4.8.2.p01.tar.gz
The file is about 16M.
Put it into your directory of choice, such as:
~/geant4
Navigate to this directory and unpack the file:
cd ~/geant4
tar -zxvf geant4.8.2.p01.tar.gz
The unpacking process will begin, starting with:
geant4.8.2.p01/
geant4.8.2.p01/ReleaseNotes/
geant4.8.2.p01/ReleaseNotes/Patch4.4.0-1.txt
geant4.8.2.p01/ReleaseNotes/Patch4.4.0-2.txt
geant4.8.2.p01/ReleaseNotes/Patch4.4.1-1.txt
And ending with:
geant4.8.2.p01/source/visualization/modeling/src/G4AttFilterUtils.cc
geant4.8.2.p01/source/visualization/modeling/src/G4HitFilterFactories.cc
geant4.8.2.p01/source/visualization/modeling/src/G4TrajectoryDrawByAttribute.cc
geant4.8.2.p01/source/GNUmakefile
geant4.8.2.p01/LICENSE
Depending on the physics of your particular application, you may need to install additional data files. These data files can be downloaded separately from the Geant4 source distribution page (the same place where you got Geant4 itself).
Create a new folder within ~/geant4/geant4.8.2.p01 to hold any of these required data files.
~/geant4/geant4.8.2.p01/data
For now, pick up the "data files for low energy electromagnetic processes":
http://geant4.web.cern.ch/geant4/support/source/G4EMLOW.4.2.tar.gz
The file is about 7.6M.
Put the file into your new data directory.
Navigate to this directory and unpack the file:
cd ~/geant4/geant4.8.2.p01/data
tar -zxvf G4EMLOW.4.2.tar.gz
The unpacking process will begin, starting with:
G4EMLOW4.2/
G4EMLOW4.2/README
G4EMLOW4.2/auger/
G4EMLOW4.2/auger/au-tr-pr-10.dat
G4EMLOW4.2/auger/au-tr-pr-11.dat
And ending with:
G4EMLOW4.2/tripdata/pp-trip-cs-9.dat
G4EMLOW4.2/photoelectric_angular/
G4EMLOW4.2/photoelectric_angular/ftab0.dat
G4EMLOW4.2/photoelectric_angular/ftab1.dat
G4EMLOW4.2/History
Doing the Initial Build
TAKE YOUR TIME AT THIS STAGE, DON'T RUSH IT.
Mistakes made at this stage can be very time-consuming to correct. Slow down.
Maybe get a cup of coffee (or a glass of wine) before you proceed. Breathe.
Finally, unless you're absolutely sure you are starting from a nice clean system, make sure you don't have any pre-existing Geant4 environment variables. You can use the "printenv" command to show all variables, and filter this with a "grep" for the string G4 as follows:
From a Terminal or xterm window:
printenv | grep G4
If any variables show up, find out what is setting them and remove them. They might be coming from your .login or .cshrc file or from some other script that you invoke upon login for some other project. Take the time now to find the cause and resolve it.
From a Terminal or xterm window:
cd ~/geant4/geant4.8.2.p01
./Configure -build
You will be asked a series of questions.
In most cases, you can just take the default response (by hitting carriage return).
But pay close attention so that you do not accept the default for the following questions:
When it says:
Could
not find CLHEP installed on this system!
Please,
specify where CLHEP is installed:
First, confirm that you have installed your CLHEP to
/u/ey/perl/CLHEP
Or wherever you've decided to keep CLHEP.
Make sure you have lib, bin and include subdirectories in that directory.
If not, recheck your CLHEP installation. If so, proceed.
Note that for this command you should use the absolute path for your CLHEP, such as:
/u/ey/perl/CLHEP
rather than a relative path, such as:
~/CLHEP
Of course, substitute your actual CLHEP path here.
Enter: /u/ey/perl/CLHEP
Take the default for everything else except:
When it asks about:
G4VIS_BUILD_OPENGLX_DRIVER
G4VIS_USE_OPENGLX
Enter: y
This tells Geant4 that you want to include the optional OpenGL Visualization driver.
When it asks about:
G4VIS_BUILD_RAYTRACERX_DRIVER
G4VIS_USE_RAYTRACERX
Enter: y
This tells Geant4 that you want to include the optional RayTracerX Visualization driver.
Take the default for everything else.
Once all of the questions have been answered, you will be told:
WARNING:
the generated configuration file
can
be edited if necessary!
You
can introduce any change to the configuration file
/u/ey/perl/geant4/geant4.8.2.p01/.config/bin/Linux-g++/config.sh
before the final installation.
To
do so, use a shell escape now (e.g. !vi
/u/ey/perl/geant4/geant4.8.2.p01/.config/bin/Linux-g++/config.sh).
Press
[Enter] to start installation or use a shell escape to edit config.sh:
At this point, what you have seen in this question and answer session should match what you find in this web directory as:
You are ready to proceed with the build.
Hit Enter.
You will then see:
Now
starting Geant4 libraries build...
On
this machine the G4SYSTEM=Linux-g++
On
this machine the G4INSTALL=/u/ey/perl/geant4/geant4.8.2.p01
On
this machine the G4TMP=/u/ey/perl/geant4/geant4.8.2.p01/tmp
On
this machine the G4LIB=/u/ey/perl/geant4/geant4.8.2.p01/lib
On
this machine the
G4LEVELGAMMADATA=/u/ey/perl/geant4/geant4.8.2.p01/data/PhotonEvaporation2.0
On
this machine the
G4RADIOACTIVEDATA=/u/ey/perl/geant4/geant4.8.2.p01/data/RadioactiveDecay3.1
On
this machine the G4LEDATA=/u/ey/perl/geant4/geant4.8.2.p01/data/G4EMLOW4.2
On
this machine the
NeutronHPCrossSections=/u/ey/perl/geant4/geant4.8.2.p01/data/G4NDL3.10
On
this machine the
CLHEP_BASE_DIR=/afs/slac.stanford.edu/www/xorg/geant4/workshops/builds/CLHEP
On
this machine the CLHEP_INCLUDE_DIR=/afs/slac.stanford.edu/www/xorg/geant4/workshops/builds/CLHEP/include
On
this machine the
CLHEP_LIB_DIR=/afs/slac.stanford.edu/www/xorg/geant4/workshops/builds/CLHEP/lib
On
this machine the CLHEP_LIB=CLHEP
On
this machine the G4VIS_BUILD_OPENGLX_DRIVER=1
On
this machine the G4VIS_BUILD_RAYTRACERX_DRIVER=1
On
this machine the G4VIS_USE_OPENGLX=1
On
this machine the G4VIS_USE_RAYTRACERX=1
On
this machine the XMFLAGS=
On
this machine the XMLIBS=
On
this machine the XMFLAGS=
On
this machine the XAWFLAGS=
On
this machine the XAWLIBS=
On
this machine the G4LIB_BUILD_STATIC=1
On
this machine the G4LIB_USE_GRANULAR=1
Starting
build...
*************************************************************
Installation Geant4 version :
geant4-08-02-patch-01
Copyright (C) 1994-2007 Geant4
Collaboration
*************************************************************
Making
dependency for file src/G4ios.cc ...
Making
dependency for file src/G4coutDestination.cc ...
Making
dependency for file src/G4VStateDependent.cc ...
Making
dependency for file src/G4VNotifier.cc ...
Making
dependency for file src/G4VExceptionHandler.cc ...
Making
dependency for file src/G4UnitsTable.cc ...
Making
dependency for file src/G4Timer.cc ...
Making
dependency for file src/G4StateManager.cc ...
Making
dependency for file src/G4SliceTimer.cc ...
Making
dependency for file src/G4PhysicsVector.cc ...
Making
dependency for file src/G4PhysicsTable.cc ...
Making
dependency for file src/G4PhysicsOrderedFreeVector.cc ...
Making
dependency for file src/G4PhysicsLogVector.cc ...
Making
dependency for file src/G4PhysicsLnVector.cc ...
Making
dependency for file src/G4PhysicsLinearVector.cc ...
Making
dependency for file src/G4PhysicsFreeVector.cc ...
Making
dependency for file src/G4OrderedTable.cc ...
Making
dependency for file src/G4LPhysicsFreeVector.cc ...
Making
dependency for file src/G4Exception.cc ...
Making
dependency for file src/G4DataVector.cc ...
Making
dependency for file src/G4AllocatorPool.cc ...
Compiling
G4AllocatorPool.cc ...
Compiling
G4DataVector.cc ...
Compiling
G4Exception.cc ...
Once you see any lines like:
Compiling G4AllocatorPool.cc ...
with no errors,
the compilation is successfully under way.
If you get a lot of warnings of the form
/usr/include/c++/3.2.3/i386-redhat-linux/bits/codecvt_specializations.h:84: warning: unused parameter `int __ibom'
just ignore them. These result from a bug in certain versions of gcc. The bug is harmless.
Adjust your machine's power management properties so that it doesn't go to sleep, and then walk away for a long long time. Wait, and wait, and wait, for the initial compilation to run.
The same information that is showing on the console is also being written to a log file so that you can review it later if necessary. The information will appear in:
~/geant4/geant4.8.2.p01/.config/bin/Linux-g++/g4make.log
An example of how this log file should look can be found in this same web directory as:
Eventually, you will see messages stating that libname.map has been built, then you will see messages about successful completion:
Libmap
stage. Searching for GNUmakefiles and sorting ...
Weeding
out paths and files ...
Making
libname.map starter file ...
Making
libname.map ...
Reading library name map file...
Reading dependency files...
Checking for circular dependencies...
Reordering according to dependencies...
Writing new library map file...
Libraries
installation completed !
####################################################
#
Your Geant4 installation seems to be successful!
#
To be sure please have a look into the log file:
#
/u/ey/perl/geant4/geant4.8.2.p01/.config/bin/Linux-g++/g4make.log
####################################################
While the Geant4 collaboration works hard to support a large variety of different Linux systems, there may be special things you need to do to make it work for your particular Linux. If you have a problem in the above build procedure, such as if your build fails to find some of the OpenGL libraries (error messages about this may include references to libXmu), look for hints in the Geant4 Installation and Configuration User Forum:
http://geant4-hn.slac.stanford.edu:5090/Geant4-HyperNews/index
Linux users are generally very helpful about documenting
such issues for each other. Your
question has very likely already been documented in that forum. If you don't find your answer there,
post it as a question.
Creating the setup script
The configure process has set up some environment variables that you will want to have in future sessions. Have configure make you an environment setup script by typing:
./Configure
(that was with no options, as opposed to ./Configure –build that you typed earlier).
You will see the following:
--- Geant4 Toolkit Installation ---
(setting environments for USER )
---------------------------------------------------
The Geant4 toolkit installation was found.
The files env.[c]sh will be copied to your current directory.
For setting Geant4 environments you should make:
source env.csh
or
. env.sh
It will also check G4WORKDIR setting and set it to
your HOME if needed.
You can use these files also for further modifications
(adding your own environments).
---------------------------------------------------
Your directory ~/geant4/geant4.8.2.p01 will now contain two scripts:
env.sh
and
env.csh
The Geant4 Work Directory
You have now built the Geant4 toolkit. If you have learned a little about
Geant4, you will know that Geant4 is not an application but rather a toolkit
from which you can build any number of applications. So before you can test Geant4, you need an example
application.
You should create a new directory, outside of your Geant4
installation area, where you will keep your example applications. This separation of spaces will help you
avoid accidentally messing up your main Geant4 installation, and will insure
that if you eventually update your main Geant4 installation (for example when a
newer Geant4 release is available), your personal application work will not be
disturbed.
Create a new directory for your work, and designate it as
your G4WORKDIR.
For example, if you want your work to be in ~/g4work and you are using C Shell or TC Shell:
setenv G4WORKDIR ~/g4work
If you are using Bourne Shell or Korn Shell:
export G4WORKDIR=~/g4work
Selecting an Example Application
You can try any of the Geant4 examples. Some suggested starting points are any of the Novice examples
~/geant4/geant4.8.2.p01/examples/novice
or the analysis example
~/geant4/geant4.8.2.p01/examples/extended/analysis/A01
Each example is described in a detailed README it the example's top level directory.
Whichever example you choose, copy it to your Geant4 work directory.
For example:
cp -r ~/geant4/geant4.8.2.p01/examples/extended/analysis/A01
$G4WORKDIR/A01
Configuring the Environment
Note that this step needs to be redone any time you start a fresh Terminal or xterm window.
If you are using C Shell or TC Shell:
setenv G4WORKDIR ~/g4work
setenv LD_LIBRARY_PATH ~/CLHEP/lib/:$LD_LIBRARY_PATH
source ~/geant4/geant4.8.2.p01/env.csh
If you are using Bourne Shell or Korn Shell:
export G4WORKDIR=~/g4work
export LD_LIBRARY_PATH=~/CLHEP/lib/:$LD_LIBRARY_PATH
source ~/geant4/geant4.8.2.p01/env.sh
It will respond:
On this machine the G4SYSTEM=Linux-g++
On this machine the G4INSTALL=/u/ey/perl/geant4/geant4.8.2.p01
On this machine the G4LIB=/u/ey/perl/geant4/geant4.8.2.p01/lib
On this machine the G4LEVELGAMMADATA=/u/ey/perl/geant4/geant4.8.2.p01/data/PhotonEvaporation2.0
On this machine the G4RADIOACTIVEDATA=/u/ey/perl/geant4/geant4.8.2.p01/data/RadioactiveDecay3.1
On this machine the G4LEDATA=/u/ey/perl/geant4/geant4.8.2.p01/data/G4EMLOW4.2
On this machine the NeutronHPCrossSections=/u/ey/perl/geant4/geant4.8.2.p01/data/G4NDL3.10
On this machine the CLHEP_BASE_DIR=/u/ey/perl/CLHEP
On this machine the CLHEP_INCLUDE_DIR=/u/ey/perl/CLHEP/include
On this machine the CLHEP_LIB_DIR=/u/ey/perl/CLHEP/lib
On this machine the CLHEP_LIB=CLHEP
On this machine the G4VIS_BUILD_OPENGLX_DRIVER=1
On this machine the G4VIS_BUILD_RAYTRACERX_DRIVER=1
On this machine the G4VIS_USE_OPENGLX=1
On this machine the G4VIS_USE_RAYTRACERX=1
On this machine the XMFLAGS=
On this machine the XMLIBS=
On this machine the XMFLAGS=
On this machine the XMLIBS=
On this machine the XAWFLAGS=
On this machine the XAWLIBS=
On this machine the G4LIB_BUILD_STATIC=1
On this machine the G4LIB_USE_GRANULAR=1
On this machine the G4UI_USE_TCSH=1
In your environment you have the G4WORKDIR=/u/ey/perl/g4work
A further note about the environment setup scripts:
The env scripts do not set every environment variable that
could be used by Geant4. They only
set those variables that you had declared to non-default values in the configure process. This works fine because any variable
that Geant4 does not find is assumed to be default. But if you are also setting some of your Geant4 environment
variables elsewhere, such as in your .login or .cshrc file, you can end up with
inconsistent results. That is why
you were strongly advised to make sure you had no pre-existing Geant4 variables
set before you began the Geant4 build.
Building an Example Application
Did you "Configure the Environment" as described above? Remember that you need to do this every time you start a new Cygwin window.
Build your example by typing:
cd $G4WORKDIR/A01
make
You will see output beginning with:
Making
dependency for file A01app.cc ...
Making
dependency for file src/A01Trajectory.cc ...
Making
dependency for file src/A01PrimaryGeneratorMessenger.cc ...
Making
dependency for file src/A01PrimaryGeneratorAction.cc ...
Making
dependency for file src/A01PhysicsList.cc ...
And ending with:
Compiling
A01Trajectory.cc ...
Creating/replacing
object files in /u/ey/perl/g4work/tmp/Linux-g++/A01app/libA01app.a ...
Compiling
A01app.cc ...
Using
granular libraries ...
Linking
A01app ...
The complete output from the above command can be found in this same web directory as:
If the build is successful, you will see the completed application file in your $G4WORKDIR directory such as:
$G4WORKDIR/bin/Linux-g++/A01app
Running
As always for a new xterm or Terminal window, configure the environment:
If you are using C Shell or TC Shell:
setenv G4WORKDIR ~/g4work
setenv LD_LIBRARY_PATH ~/CLHEP/lib/:$LD_LIBRARY_PATH
source ~/geant4/geant4.8.2.p01/env.csh
If you are using Bourne Shell or Korn Shell:
export G4WORKDIR=~/g4work
export LD_LIBRARY_PATH=~/CLHEP/lib/:$LD_LIBRARY_PATH
source ~/geant4/geant4.8.2.p01/env.sh
This might be good time to check that your XWindows setup is correct for our purposes.
If you are running Geant4 on a remote machine (using the machine in front of you just as a terminal), make sure you have your XWindows client running.
Make sure your terminal is correctly set to accept connections from the machine where you are running Geant4.
You might need to explicitly set display from the machine on which you are running Geant4 to make it display to you terminal.
It is beyond the scope if this tutorial to advise on all XWindows problems, but it is always helpful to try a test with a simple application such as xclock.
Then, to run your example, cd to the example's top level directory, such as:
cd $G4WORKDIR/A01
And from there, run the newly created executable:
$G4WORKDIR/bin/Linux-g++/A01app
You will see a response that starts with:
*************************************************************
Geant4 version Name:
geant4-08-02-patch-01
(23-February-2007)
Copyright : Geant4 Collaboration
Reference : NIM A 506 (2003), 250-303
WWW : http://cern.ch/geant4
*************************************************************
Visualization
Manager instantiating...
Visualization
Manager initialising...
Registering
graphics systems...
You
have successfully registered the following graphics systems.
Current
available graphics systems are:
ASCIITree (ATree)
DAWNFILE (DAWNFILE)
GAGTree (GAGTree)
G4HepRep (HepRepXML)
G4HepRepFile (HepRepFile)
RayTracer (RayTracer)
VRML1FILE (VRML1FILE)
VRML2FILE (VRML2FILE)
OpenGLImmediateX (OGLIX)
OpenGLStoredX (OGLSX)
RayTracerX (RayTracerX)
And ends with:
EMcalorimeterPhysical[0]
EMcalorimeterLogical 1 CsI
cellPhysical[-1] cellLogical 0 CsI /EMcalorimeter
HadCalorimeterPhysical[0]
HadCalorimeterLogical 1 Lead
HadCalColumnPhysical[-1] HadCalColumnLogical 1 Lead
HadCalCellPhysical[-1] HadCalCellLogical 1 Lead
HadCalLayerPhysical[-1]
HadCalLayerLogical 1 Lead
HadCalScintiPhysical[0] HadCalScintiLogical 0 Scintillator
/HadCalorimeter
Idle>
The complete output from the above command can be found in this same web directory as:
If it fails to run, claiming it can't find CLHEP.so, you probably missed the
setenv LD_LIBRARY_PATH ~/CLHEP/lib/:$LD_LIBRARY_PATH
Fix that and try to run again.
Make sure your output included a mention of the graphics systems:
OpenGLImmediateX (OGLIX)
OpenGLStoredX (OGLSX)
If those didn't show up, you have missed something in the above instructions.
Did you correctly answered the questions about OpenGL in the ./Configure -build procedure?
Did you get error messages during that procedure?
Did you follow the instructions in the above section, "Creating
the setup script"?
Did you follow the instructions above about "As always
for a new xterm or Terminal window, configure the environmentÉ."?
If you still can't figure out why you don't have OpenGL, you
can still proceed, but you will have to use some other graphics driver. See some notes a little later in this
document about how to use the HepRepFile driver.
From here, we'll assume you have OpenGL successfully loaded.
From the idle prompt, visualize the example by typing the following:
/vis/open OGLIX
/vis/drawVolume
You will get the following response:
Got
standard cmap
Window
name: viewer-0 (OpenGLImmediateX)
WARNING:
objects with visibility flag set to "false" will not be drawn!
"/vis/viewer/set/culling global
false" to Draw such objects.
Also see other
"/vis/viewer/set" commands.
WARNING:
SceneHandler "scene-handler-0", to which viewer "viewer-0"
is attached, has no scene -
"/vis/scene/create" and"/vis/sceneHandler/attach"
(or use compound command
"/vis/drawVolume").
WARNING:
For systems which are not "auto-refresh" you will need to
issue "/vis/viewer/refresh"
or "/vis/viewer/flush".
And an OpenGL window will appear and the example geometry will be drawn, as in:
To add trajectories and hits to the visualization, and then run an event:
/vis/scene/add/trajectories
/vis/scene/add/hits
/run/beamOn 1
You will then see something like:
When you are finished with your Geant4 session, just type:
exit
For more details on using OpenGL for Geant4, see:
http://geant4.slac.stanford.edu/Presentations/vis/G4OpenGLTutorial/G4OpenGLTutorial.html
Here's another example. This one makes output go to a HepRep file, suitable for viewing in the HepRApp HepRep Browser:
$G4WORKDIR/bin/Linux-g++/A01app
/vis/open HepRepFile
/vis/drawVolume
/vis/viewer/flush
/vis/scene/add/trajectories
/vis/scene/add/hits
/run/beamOn 1
For more details on using HepRApp for Geant4, see:
http://geant4.slac.stanford.edu/Presentations/vis/G4HepRAppTutorial/G4HepRAppTutorial.html
Note: HepRApp and Geant4 do not have to run on the same machine. You can copy the .heprep file from the Geant4 machine to the machine with HepRApp, or you can simply make the .heprep file visible from the web, and let HepRApp pick it up via the url.
Also note that the .heprep file can be zipped to about 5
percent of original size and HepRApp can then read in the zipped version (you
don't need to unzip the file).
You now have Geant4 installed and have demonstrated a few examples using two different visualization systems.
Single versus Multi-User Installation
The above instructions assumed you were doing a single-user installation. They had you keep all of the build products in the same area as your CLHEP and Geant4 source. Note however that both of these packages support standard multi-user installation processes.
For CLHEP, just specify a different value for "--prefix".
For Geant4, when ./Configure -build asks you to "Specify the path where Geant4 libraries and source files should be installed", specify whatever area you want instead of taking the default. When you are asked about the CLHEP library, be sure to specify the same location that you specified during the CLHEP installation. Then, after you've installed Geant4 as described below, issue an additional command (as root user), ./Configure -install.
I hope these instructions have been helpful.
If you find any problems or can suggest corrections, please let me know.
Joseph Perl
Stanford Linear Accelerator Center
1 June 2007