Michigan Test Page

This page is to the responsivenss of the wiki. It has no other purpose.

• My text goes here

---

• Let us DO another bullet

1. Item 1
2. Item 2
3. Item 3

ATLAS Software Setup at Michigan

Overview

We have installed an Atlas mirror and the Athena 12.0.2 installation kit on the Michigan cluster. The mirror is the software repository, from which ATLAS installation kits may installed. The kit installations have the actual Athena software which users run. One can install ATLAS installation kits using the UM mirror to other machines directly from the UM mirror.

The Athena installation kits provide a run-time environment for Athena and related software like CMT and pool. They do not provide CVS access to edit/update Athena code at CERN (however, you can still edit/compile private code).

At present I have only installed the 12.0.2 Athena kit. I attempted a "Multi" installation of all kits from 11.2.0 onward, but this did not work. In principle, other individual kits could be installed if desired. I will update the installation with new versions of Athena as they become available.

Location

All the software is installed at

/afs/atlas.umich.edu/atlas/software/kits

For brevity I will call this location $KITS from now on.

i. The pacman installation program is installed in $KITS/pacman This program is used to install/upgrade the ATLAS mirror and installation kits.

ii. The ATLAS mirror is installed at $KITS/ATLAS.mirror. Kit installations use this mirror to get the software using mirror name am-UM or by using the full pathname /afs/atlas.umich.edu/atlas/software/kits/ATLAS.mirror.

iii. The ATLAS kit installations are installed in various ATLAS Athena project directories which have names beginning with the prefix "Atlas", for example $KITS/AtlasAnalysis. These are the same directories as one sees in the "builds" area on lxplus or bnl. There are are other directories like CMT and usr for other software installed by the kit.

You can quickly check which Athena versions are installed by looking in any of the "Atlas" project and looking at the numbered subdirectories. These subdirectories are 10 less than then Athena version (e.g. subdirectory 2.0.2 = Athena 12.0.2 [however, this correspondence may eventually be broken])

Using the ATLAS software.

One of the beauties of Athena is that there are many variations on how to do the setup. Here I give one simple way, but it is certainly not the only possibility.

First-time Athena set up.

1. First you need to create a requirements file and the setup scripts used by CMT to configure for a specific ATLAS release. CMT is a configuration management environment to manage the Athena code. There is a script create-cmthome.sh which will do this for you. Here is what you do:

cd /afs/atlas.umich.edu/atlas/software/kits ./create-cmthome.sh

Running this script will create a directory $HOME/cmthome ($HOME is you home directory) and put in this directory files requirements, setup.(c)ch, and cleanup.(c)sh. This step only needs to be repeated when the CMT version is changed, which does not happen very often.

2. Create directories $HOME/testarea and $HOME/testarea/AtlasOffline-12.0.2.

The directory $HOME/testarea is the "Athena test area" for Athena running. You can choose a different name for this directory by editing $HOME/cmthome/requirements and changing the ATLAS_TEST_AREA line.

Each version of Athena you want to run must have its own subdirectory named AtlasOffline-XX.Y.Z where XX.Y.Z is the Athena version, such as 12.0.2. Of course, you only need to create these directories once.

Note that you can edit the requirements file to override these default names and do all kinds of fancy stuff and/or have multiple requirements files in directories other than $HOME/cmthome to allow many types of Athena setups.

Set up to run a specific Athena release - done each login

1. Configure CMT to use release 12.0.2:

cd $HOME/cmthome source setup.(c)sh -tag=12.0.2

2. Run the Athena runtime script:

source /afs/atlas.umich.edu/atlas/software/kits/AtlasOffline/12.0.2/AtlasOfflineRunTime/cmt/setup.csh

3. Create a "run" directory

cd $HOME/testarea/AtlasOffline-12.0.2 mkdir run cd run

This "run" directory (which can have any name) is the directory from which you run Athena. Typically you need an "options" file which tells Athena what to do. For testing purposes you can use the HelloWorldOptions.py options file which does a short test run of Athena. You can get this file with the get_files command which searches for a specific file in the Atlas builds directories. (Note one stupid feature of this program - it does not inform you if it fails to find a file, you just have to notice that it did not work). Anyway do this:

get_files HelloWorldOptions.py
athena HelloWorldOptions.py

and you get should get various HelloWorld messeges printed to the screen.

-- EdwardDiehl - 08 Sep 2006