...
Type "alias" command to see additional "localSetupXXXX" commands.
JupyterLab
JupyterLab environment is also available at http://jupyter.slac.stanford.edu. Login with your SLAC Unix account. You can choose any JupyterLab environments available from that page (some of them will allow access to the GPU resources), though only the ATLAS image will mount your GPFS home directory and data directory. The ATLAS image provides PyROOT and JupyROOT (ROOT C++) notebooks with capability to access remote data via the Xroot (root) protocol or webdav (http) protocol. It also includes several Machine Learning software package. It also allows storing notebooks to Google Drive for portability.
- This is an area that SLAC and the Analysis Computing Facility is constantly looking to improve. Please give us your feed back sending e-mail to SLAC ACF mailing list atlas-us-slac-acf@cern.ch
Remote X window access
Please refer to SLAC's FastX page
for detail instructions.
...
- From the interactive login machines, one can browse the Xrootd storage by cd /xrootd/atlas on RHEL6 interactive login nodes
- From batch jobs, one can't list directory in the Xrootd storage. But can access files via
root://atlrdr1//xrootd/atlas/... - Using the rucio tools, one can list ATLAS datasets that are already in the Xrootd storage system via command rucio list-datasets-rse <RSE>, where RSE can be SLACXRD_DATADISK, SLACXRD_LOCALGROUPDISK, SLACXRD_SCRATCHDISK.
...
SLAC uses LSF batch system. LSF replica your current environment setup when submitting jobs. This includes your current working directory and any Unix environment variable setups. 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 the 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.
...
Manage jobs
Use bjobs, or bjobs -l <JOBID> to get detailed info about a specific job.
...
Use bkill <JOBID> to kill a job
...
- For details about those LSF commands and their options, please refers to the man pages of "bsub", "bjobs", "bkill".
More info on LSF
...
- information regarding high performance computing clusters, including LSF related documents and best practices, please refer to the SLAC High Performance Computing page.
Resource monitoring
Coming soon