Page History

...

There are 5 fields that need to be filled. They are listed below:

1. A personal script defining some environment variables related to the software to use (CMTPATH, GLAST_EXT...). One can use the scripts which were listed in section 1 of this web page (examples: BeamtestRelease-v3r0907p2.sh, EngineeringModel-v6r070329p16.sh BeamtestRelease-v4r0909p2.sh , EngineeringModel-v6r070329p16.sh)

1. A "Gaudi" configuration script. The name of this script is setup.sh and its location depends on the software package to be used. An example follows: BeamtestRelease-v3r0907p2: /nfs/farm/g/glast/u09/builds/rh9_gcc32opt/BeamtestRelease/BeamtestRelease-v3r0907p2/Gleam/v6r18/cmt/setup.sh ; EngineeringModel-v6r070329p16: /nfs/farm/g/glast/u09/builds/rh9_gcc32opt/EngineeringModel/EngineeringModel-v6r070329p16/Gleam/v6r8p1/cmt/setup.sh

1. A "Gaudi" executable (. This is the Gleam executable), Gleam.exe; and its location depends on the software package that is used. BeamtestRelease-v3r0907p2: /nfs/farm/g/glast/u09/builds/rh9_gcc32opt/BeamtestRelease/BeamtestRelease-v3r0907p2/Gleam/v6r18/rh9_gcc32opt/Gleam.exe; EngineeringModel-v6r070329p16: /nfs/farm/g/glast/u09/builds/rh9_gcc32opt/EngineeringModel/EngineeringModel-v6r070329p16/Gleam/v6r8p1/rh9_gcc32opt/Gleam.exe

1. A job options ascii file. This file definingdefines, among other things, the input data and geometry to be used. It is slightly different for different software package versions. Examples follow:

1. A working directory

Important Remark

FRED requires to run the script in a BASH shell, therefore the sripts used in the GLAST panel must BASH scripts.

 BeamtestRelease-v4r0909p2.sh

jobOptions_beamtest.txt
-rw-r-r-   1 dpaneque  dpaneque  1929 Aug  3 13:55 jobOptions_EngineeringModel.txt

 [BeamtestRelease-v4r0909p2.sh|^BeamtestRelease-v4r0909p2.sh] for bash )   \[\] ([EngineeringModel-v6r070329p16.sh|^EngineeringModel-v6r070329p16.sh]