ATLAS Environment at SLAC

This page describes how to have your environment configured to run ATLAS jobs at SLAC. It also tries to explain where you may need to do something different. For first time SLAC computing users, you need to first register as a SLAC user and obtain a SLAC computing account. The initial account setup related info can be found on the US Western Tier-2 page along with other info on local computing at SLAC. Among the various public machines at SLAC, the recommended interactive machines to login are the RHEL4 nodes:

ssh RHEL4-32.slac.stanford.edu

Some essential background to the ATLAS software setup at SLAC:

The ATLAS software installation at SLAC is the 'Pacman kits' which includes the sharable libraries, but not the full release tree with code of all packages. However, the code can be easily browsed on the web through LXR or go to more detail viewcvs (what you most likely need should be in the offline folder). See `Default release' section below for further details on the SLAC local release setup.
For code development on working packages, the default operating setup is to use the CERN CVS repository, via ssh. The Kerberos setup is not yet established at SLAC so that you need to make a simple manual environment definition for CVSROOT (see the `CVSROOT' section below) in your login (add to your .bshrc). See here for a more automated way of handling CVS.
In case you have not yet done so, some orientations about setting up CERN account may help.
bash is the preferred shell to use with ATLAS code at SLAC. If another shell is your default at login, that's fine - just type "bash" to start the bash shell when you're ready to start your ATLAS work.
The recent WT2 Users Forum had many relevant talks.

If you have any questions please post them to the Non-Grid Jobs at SLAC Forum in the ATLAS Hypernews system, where all local ATLAS computing issues at SLAC are discussed.

Activate ATLAS Login

To turn on the ATLAS login you can do it one of two ways, below. Next time you login using bash, the ATLAS commands should be in your path. You need to use the HEPiX login to get the general SLAC setup (so things like LSF can be used).

Make ATLAS your HEPiX preferred login

In this case there are three steps required to get it working correctly. If you've already set your account up for HEPiX login (because you use to work on BaBar for instance) then you only need to do that last step.

Add the following lines to your .bashrc file

#####################################################
# Do HEPiX login
if [ -r /usr/local/lib/hepix/central_env.sh ]; then
    source /usr/local/lib/hepix/central_env.sh
fi
#####################################################

Add the following to your .profile file

###########################################################
# Do HEPiX login
if [ -r /usr/local/lib/hepix/central_login.sh ]; then
         source /usr/local/lib/hepix/central_login.sh
fi
###########################################################

Then create a file like the following one
```
echo "atlas" > .hepix/preferred-group
```
Create an ATLCURRENT file in your $HOME directory.

If you would like to not setup a preferred release by default, have this file contain the word "none".
This is the suggested configuration... you can then easily setup different releases for different projects simultaneously.
```
echo "none" > ATLCURRENT
```

Please continue on to the next page to complete the rest of the setup.

Differences at SLAC

atladdpkg

Amir Farbin wrote a script he called addpkg (to mimic a BaBar script of the same name) to allow you to check out a package without knowing the tag if you wanted the same version as was in the release. I've created a new version that works using a cmt command (suggested by Zach Marshal).

Disk Space and datasets

Information on this is available on another page now.

CVSROOT

If your user name is different between SLAC and CERN you'll need to set CVSROOT to include your CERN user name. By default it is set to :ext:atlas-sw.cern.ch:/atlascvs. You should set it by adding the following to your .bashrc file

CVSROOT=:ext:<CERNusername>@atlas-sw.cern.ch:/atlascvs
CVS_RSH=ssh
export CVSROOT
export CVS_RSH

You should of course replace <CERNusername> with your CERN username.
Beware, setting up a release can ofter destroy your CVSROOT and CVS_RSH settings, so you have to set them again after setting up your release.

dq2-*

Now you should be able to run any dq2-* commands from any machine. The commands are setup when you type "bash".
For instance:

bash
voms-proxy-init -voms atlas
dq2-put --long-surls -s /xrootd/atlas/usr/f/fizisist/test user.DavidWilkinsMiller.misal1_csc11.005009.J0_pythia_jetjet.pile1sf01.AOD.v13003003.verylow.TEST9

dq2-ls -f user.DavidWilkinsMiller.misal1_csc11.005009.J0_pythia_jetjet.pile1sf01.AOD.v13003003.verylow.TEST9

cd /tmp
dq2-get user.DavidWilkinsMiller.misal1_csc11.005009.J0_pythia_jetjet.pile1sf01.AOD.v13003003.verylow.TEST9

ls -l user.DavidWilkinsMiller.misal1_csc11.005009.J0_pythia_jetjet.pile1sf01.AOD.v13003003.verylow.TEST9/

Please see more information here.

Last edited by Andy Haas on April 6, 2009.