Introduction to Running Glast Gaudi Executables

Runnning Gaudi Programs

There are a number of GLAST executables that we have created, that are based on Gaudi.  The following is an explanation of their common elements.

Gaudi Executables

The Gaudi executables are generally quite simple.  They have two principal tasks

1. Specifying where the Job Options file is.

2. Creating an instance of the Gaudi Application Manager and getting it to run, using the Job Options file.

Specifying the Job Options File

There are two different conventions that we have in place to specify to the executable where the Job Options file is

1. The Gaudi executable assumes that the Job Options file is either

    ${PACKAGEROOT}/src/jobOptions.txt

   or

    ${PACKAGEROOT}/src/test/jobOptions.txt

   If the executable you are interested in uses this convention, then, if you want to edit the Job Options file, then you need to edit the pre-existing copy.

    

2. Many executables have been set up to look for an environment variable ('JOBOPTIONS'), which is used to specify where the Job Options file is.  Setting this environment variable is done in the CMT requirements file for the package in question.  So, for the package pdrApp, we find the following definition in it's requirements file.

   set JOBOPTIONS ${PDRAPPROOT}/src/jobOptions.txt

    

3. Some executables accept an input parameter.  The first input parameter is typically the path and name of a jobOptions file to use.

Documentation on Individual Executables

General information about the Job Options file is available from the Gaudi site, or from our Gaudi FAQ.

Detailed information about the individual Job Options files for each Gaudi program is also available

T. Lindner Last Modified: 2002-03-20 14:37:31 -0800