Tutorial Setup at Home Institution

WARNING: This page is obsolete.

Please look at https://atlas-software.docs.cern.ch/software-infrastructure/platforms-compilers/ or use Containers

These instructions are for setting up for the tutorial on a computer at your home institution. You should do this prior to the tutorial. To do these, log in to your computer and follow these instructions.

Please note that you may have to revert to lxplus if there are unresolved problems on your computer so we suggest you leave open a terminal session to lxplus and type in the equivalent commands.

Unix Shell

We recommend your shell be bash but not csh or other c-shell flavors. To check which shell you are using, do

ps -p $$

Grid Certificates

Make sure your grid certificates are visible in ~/.globus. For example, you should see the following protections:

ls -l ~/.globus
total 9
6 -rw-r--r--  1 desilva zp 5711 Oct 23  2007 usercert.pem
1 -rw-------  1 desilva zp  963 Oct 23  2007 userkey.pem

Software

You need to have the appropriate software already installed; in particular, you will need to have

• gLite
• DQ2Client

Athena 14.1.0.3

The Athena release used will be 14.1.0.3 and you will need to ensure that this is available on your machine; if not, you can install it as a Kit. Note that you will need Pacman).

First test that your computer is ATLAS-ready. Next, select your nearest mirror (http://pacman.atlas-canada.ca/ATLAS.mirror, am-CERN, am-BNL, etc; or get the pacball).

Next, install 14.1.0 as described in this Kit installation page.

Then, install the 14.1.0.3 AtlasProduction cache as described in this Cache installation page.

Now, note the location of your 14.1.0 installation directory; in the example above, it is <Athena-Installation-Directory>/14.1.0; this will be set as SITEROOT in your requirements file below.

Vancouver-14.1.0.3

In addition, your computer will need access to the group area Vancouver-14.1.0.3 ( reference); instructions to do this are summarized below (you will need Pacman as before.):

    cd <Athena-Installation-Directory>
    mkdir -p GroupArea/Vancouver-14.1.0.3
    cd GroupArea/Vancouver-14.1.0.3
    yes | pacman -get http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/PAT/EventView/:Vancouver-14.1.0.3.pacman
    ln -s . 14.1.0.3

Now, note the location of your Vancouver-14.1.0.3 installation; in the example above, it is <Athena-Installation-Directory>/GroupArea/Vancouver-14.1.0.3; this will be set as ATLAS_GROUP_AREA in your requirements file below.

You need to know ...

Before you proceed any further, you will need to know the following information:

• what to source and setup the gLite environment (if this was installed by the system administrator with yum, it may already be setup when you login; type 'which voms-proxy-init' to see if it is available).
• what to source and setup the DQ2Client environment
• the location of Athena 14.1.0
• the location of CMT/v1r20p20080222/mgr/setup.sh (this should be in the Athena 14.1.0 release)
• the location of the group area for Vancouver-14.1.0.3

Requirements

(If you have a ~/cmthome directory, you may want to temporarily rename it for the duration of the tutorial.) Create a file ~/cmthome/requirements. An example can be viewed here.

Edit the file and change SITEROOT and ATLAS_GROUP_AREA to point to the 14.1.0 and Vancouver-14.1.0.3 locations respectively. Next source the setup scripts:

source <Path to the 14.1.0 release>/CMT/v1r20p20080222/mgr/setup.sh
cmt config

You should not see any errors or warnings at this stage; if you do, something is wrong. Some possibilities to check (see the requirements file): ATLAS_DIST_AREA and ATLAS_GROUP_AREA actually exists

Next, do the setup (do this in a new session; this will be the starting point each time you want to work):

source ~/cmthome/setup.sh -tag=14.1.0,AtlasProduction,groupArea

Again, you should not see any errors or warnings here. If you do, check also that $TestArea does not exist (do an ls); if it does, delete or move it and repeat the above command.

From this point on, you should be ready for the tutorial. However, it will be prudent to check by checking out some packages and compiling as described in the Tutorial setup.

You may then want to run this script to test the configuration.

-- AsokaDeSilva - 16 May 2008