Running Workbook Examples

If you use a different release for testing the workbook examples, you may need different versions of packages checkedout. Please see this section for details on how to determine the package versions.

Example requirements file

This is an example of a requirements file which lives in ~/cmthome:

set CMTSITE STANDALONE
set SITEROOT /data/Kits/13.0.20/
macro ATLAS_DIST_AREA ${SITEROOT}
macro ATLAS_TEST_AREA ${HOME}/testarea 
apply_tag projectArea
macro SITE_PROJECT_AREA ${SITEROOT}
macro EXTERNAL_PROJECT_AREA ${SITEROOT}
apply_tag setup
apply_tag simpleTest
use AtlasLogin AtlasLogin-* $(ATLAS_DIST_AREA)
set CMTCONFIG i686-slc4-gcc34-opt
set DBRELEASE_INSTALLED 3.1.1

Note that this is for Scientific Linux 4.

Here is another example of a requirements file:

set CMTSITE STANDALONE

macro PROJ_RELEASE   "latest" \
              12.0.6         "12.0.6" \
              13.0.20        "13.0.20"

set SITEROOT /data/Kits/${PROJ_RELEASE}

macro ATLAS_DIST_AREA ${SITEROOT}
macro ATLAS_TEST_AREA ${HOME}/testarea
apply_tag projectArea
macro SITE_PROJECT_AREA ${SITEROOT}
macro EXTERNAL_PROJECT_AREA ${SITEROOT}
apply_tag setup
apply_tag simpleTest
use AtlasLogin AtlasLogin-* $(ATLAS_DIST_AREA)
set CMTCONFIG i686-slc4-gcc34-opt
set DBRELEASE_INSTALLED 3.1.1

This allows one to switch releases without having it "hardcoded" in SITEROOT. For example, I can then setup as

source ~/cmthome/setup.sh -tag=13.0.20,32    (for 13.0.20 32-bit)
source ~/cmthome/setup.sh -tag=12.0.7,gcc323 (for 12.0.7 running gcc 3.2.3)

Note that the SITEROOT directory should at least have a softlink "latest" to one of the new releases. Also, if you change the requirements file, remember to do a cmt config.

Environment Variables

• CVSROOT should be automatically setup to point you to

:kserver:atlas-sw.cern.ch:/atlascvs

Tasks at Each Login

• Setup the cmt configuration

~/cmthome/source.[c]sh -tag=xx.xx.xx[,32] 

• (do this, or the *.csh version only if you install the gLite single-user version)

source ~/gLite/etc/profile.d/grid_env.sh
source ~/gLite/etc/profile.d/lcgenv.sh

• Ganga setup is not needed ...

(for bash) export GANGA_CONFIG_PATH=GangaAtlas/Atlas.ini
(for tcsh) setenv GANGA_CONFIG_PATH GangaAtlas/Atlas.ini

• set the environment variable for EDITOR

(for bash) export EDITOR=emacs
(for tcsh) setenv EDITOR emacs

• authenticate Kerberos if you want access to source code

kinit -4 -5 user@CERN.CH

• authenticate afs if you want to write to your CERN afs area

klog

• get the grid proxy

 voms-proxy-init --voms atlas:/atlas/ca

Please see also this link.

-- AsokaDeSilva - 28 Sep 2007