Page History

...

• I set up an area in my Glast Users area
  e.g. . For example

  No Format
  $USHERNFS/RealData

  where USHERNFS is /nfs/slac/g/glast/users/glground/usher

...

• Set CMTPATH. Here it is convenient to point to one of the builds already done for us by the Release Manager. You can find the specific paths on the Release Manager page . Pick one of the builds and you will see the path to it on the resulting page. Set the CMTPATH:
  in csh:

  No Format
  setenv /nfs/farm/g/glast/u09/builds/rh9_gcc32/GlastRelease/GlastRelease-HEAD1.420

  in bash:

  No Format
  CMTPATH=/nfs/farm/g/glast/u09/builds/rh9_gcc32/GlastRelease/GlastRelease-HEAD1.420; export CMTPATH

• Setup the Gleam environment. Batch jobs inherit the environment of the submitting process. So, "source" the setup file (note that you will need to check the Gleam version number to do this):
  in csh:

  No Format
  source $CMTPATH/Gleam/(gleam version)/cmt/setup.csh

  in bash:

  No Format
  source $\{CMTPATH}/Gleam/(gleam version)/cmt/setup.sh

• Setup the top level job options environment variable to point to your top level job options file. For example:
  in csh:

  No Format
  setenv JOBOPTIONS $USHERNFS/RealData/readdigi_runrecon.txt

  in bash:

  No Format
  JOBOPTIONS=$\{USHERNFS}/RealData/readdigi_runrecon.txt; export JOBOPTIONS;

• Before you can run a job you need to reset the permissions (why?)

  No Format
  chmod u+=rwx *

  
  

  chmod g+=rw *

  does the trick for me.

Submit the batch job

• Use "bsub" to submit to the batch system (see the Glast batch farm page for more information):

  No Format
  bsub -q long -o $USHERNFS/RealData/recon.out $CMTPATH/Gleam/v5r8

  
  

  p1/rh9_gcc32/Gleam.exe

• use "bjobs" to check on the status of the job

...