SLAC uses the LSF (Load Sharing Facility) batch system. LSF replica your current environment setup when submitting jobs. This includes your current working directory and any Unix environment variable setups. All batch nodes available to the ATLAS users have CVMFS, outbound network connectivity, and access to SLAC networked storages. They also have large /scratch space for temporary use (please clean up your files from there after your job finishes). The following are examples of using LSF:
Submit a job.
$ cat myjob.sh #!/bin/sh #BSUB -W180 pwd echo "hello world" $ bsub < myjob.sh Job <96917> is submitted to default queue <medium>.
This will submit a job to LSF. The "pwd" command will print out the job's working directory, which should be the same directory where this job is submitted. The #BSUB -W180 directive tells LSF that the job's maximum run time limit (wall clock time) is 180 minutes. After that the job will be killed. If #BSUB -Wnnn isn't specified, your job get the default, which is 30 minutes. You can but don't have to specify a batch queue. If no queue is given at the submission time, LSF will choose one for your job according to job's run time limit.
Check job status.
Check status of all my job
...
SLAC batch resources consist of several generation of hardwares. They are listed at the the shakeholder's priority page. These batch nodes all have CVMFS, outbound network connectivity, and access to SLAC networked storages. They also have large /scratch space for temporary use (please clean up your files from there after your job finishes) Some of the batch nodes run RHEL 6 operation system, while others run CentOS 7 operation system. Singularity container technology is available on the CentOS 7 batch nodes.
...