From Documentation
Revision as of 10:21, 26 March 2012 by Isaac (Talk | contribs) (Created page with "{{Software |package_name=AMBER |package_description=Suite of programs that allow users to carry out molecular dynamics simulations |package_idnumber=57 }} The latest version of ...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Description: Suite of programs that allow users to carry out molecular dynamics simulations
SHARCNET Package information: see AMBER software page in web portal
Full list of SHARCNET supported software

The latest version of geant4 (9.5) is installed on CentOS clusters (see the table at the top of this page) under _/opt/sharcnet/geant4/9.5/gcc_. We also have the older version 4.9.1 installed on some systems, but it is no longer updated, so for the newest geant4 please log in to the CentOS clusters.

Geant4 comes with many examples useful for testing purposes. You can start with a simple test. For instance, here are the steps to compile and run an analysis example A01 in ~/testing directory inside your home directory:

module unload intel/11.0.083
module load gcc/4.5.3 
module load geant4/gcc/9.5
export G4WORKDIR=~/testing
cp -a /opt/sharcnet/geant4/9.5/gcc/examples/extended/analysis/A01 $G4WORKDIR/A01
source /opt/sharcnet/geant4/9.5/gcc/share/Geant4-9.5.0/geant4make/
export CXX=g++
cd $G4WORKDIR/A01 
make # LD_RUN_PATH is ignored by this makefile, so need to set LD_LIBRARY_PATH
export LD_LIBRARY_PATH=/opt/sharcnet/gcc/4.5.3/lib64:$LD_LIBRARY_PATH
sqsub -q serial -r 5m -o output.log ../bin/Linux-g++/A01app

Note that geant4 makefiles will omit the environment variable $LD_RUN_PATH which has a path to gcc libraries, instead encoding only its own path to the application library you are building ($G4WORKDIR/tmp/Linux-g++/A01app in our example), so we need to set LD_LIBRARY_PATH by hand before running geant4 as illustrated by the example above.