You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 13
Next »
Set up a working area on linux
- I set up an area in my Glast Users area. For example
where USHERNFS is /nfs/slac/g/glast/users/glground/usher
- Use this space to store the top level job options file for controlling the job (I still rely on the basicOptions file as much as possible)
Setting up the environment
- 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:
in bash:
- 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:
in bash:
- Setup the top level job options environment variable to point to your top level job options file. For example:
in csh:
in bash:
- Before you can run a job you need to reset the permissions (why?)
does the trick for me.
Submit the batch job
- use "bjobs" to check on the status of the job
In theory this can be done from a shell script...
- But I could not get the following to work. Basically, when I source readdigi_runrecon.csh it tells me that it can't find Gleam, essentially because the CMTPATH is undefined.
What can I say other than it is for these types of reasons that I don't like linux...
TkrGroup