AMA in Athena 14 1 0

From Atlas Wiki
Revision as of 12:20, 9 June 2008 by Salaman (talk | contribs)
Jump to navigation Jump to search

Setting up ATLAS Release 14.1.0 at NIKHEF

Only once:

  • Create a file: $HOME/cmthome/requirements (and modify <username>)
    set SITEROOT /data/atlas/offline/14.1.0
    macro ATLAS_TEST_AREA /project/atlas/users/<username>
    apply_tag projectArea
    apply_tag opt
    apply_tag setup
    apply_tag simpleTest
    use AtlasLogin AtlasLogin-* $(ATLAS_DIST_AREA)
    set CMTCONFIG i686-slc4-gcc34-opt
  • $ source /data/atlas/offline/14.1.0/CMT/v1r20p20080222/mgr/
  • $ cmt config in $HOME/cmthome

Everytime you log on:

$ source $HOME/cmthome/ -tag=14.1.0,32


To obtain the code, do the following: in /project/atlas/users/<username>/14.1.0/PhysicsAnalysis:

$ cvs -d /project/atlas/cvs/Athena co -r HEAD AtlasModularAnalysis

Compile the code as follows

$ cd AtlasModularAnalysis/cmt
$ cmt config
$ .
$ gmake

There are three ways of running AMA:

  • Standalone (no AODs)
  • with ARA (all formats)
  • in Athena (only AODs) Use this for FDR-II

Using AMA within Athena (AMAAthena)

NB: All AtlasRelease (athena) compilation and runtime activities should be perform only in the bash shell

To set up the runtime environment for AMAAthena in conjuction with the grid file stager do the following from a clean shell.

$ source /global/ices/lcg/current/etc/profile.d/
$ voms-proxy-init
(your pass phrase goes here)
$ source $HOME/cmthome/ -tag=14.1.0,32
$ export TMPDIR=/tmp  

This specific order is required to avoid a python clash between the grid middleware and the ATLAS release environment. The above sequence of command is required before you set up the AMA and AMAAthena code (as explained below) as well as everytime you login and want to run AMAAthena.

How to retrieve AMAAthena code and how to compile it

First install the AMA code itself as explained in the previous section. Then, starting in /project/atlas/users/<user>/14.1.0/PhysicsAnalysis do the following:

$ cd /project/atlas/users/<user>/14.1.0/PhysicsAnalysis
$ cvs -d /project/atlas/cvs/Athena co -r AMAAthena-V00-00-02 AMAAthena
$ cd AMAAthena/cmt
$ cmt config
$ .
$ gmake

How to run AMAAthena code

run AMAAthena as follows in the run/ directory of the AMAAthena package

$ athena

The above jobOptions files is configured to run OK with both local files (e.g. in /data/atlas) and using the file stager (on the Tier-1). The stager infrastructure is automatically activated as soon as any file with the prefix 'gridcopy:' is found in the InputCollections definition. Examples for both modes of operation are included

To run AMAAthena in batch on stoomboot use the bsub script that is present in the run directory

$ ./bsub athena

Note that the bsub included in run/ here was modified to be pure bash to avoid csh problems related ATLAS releases. Any earlier private copies you may have will not work.

Using AMA Standalone

$ gmake -f Makefile.Standalone amacint
$ gmake -f Makefile.Standalone CSCDriver

Using AMA with ARA

from kit

(no extra tags) in AtlasModularAnalysis/cmt

$ cmt config
$ source
$ gmake

with recommended tags

(see also: ):

  • copy files from /data/atlas/users/gossie/Athena/14.1.0
  • compile (NB: use 'cmt bro gmake' to take care of dependencies ) (in all */cmt directories)
    $ cmt config
    $ source
    $ gmake



source in AtlasModularAnalysis/cmt directory gives crash when running AMA with ARA.

Solution: do another source in the AthenaROOTAccess/cmt directory. Now you can run AMA with ARA without problems again.


Sometimes ARA crashes just after initialisation. This is due to a wrongly set PYTHONPATH. To correct this:

  • Copy /data/atlas/users/gossie/Athena/ to anywhere you like
  • replace <username> with your username
  • $ source

running i686-slc4-gcc34-opt/CSCDriver.exe should be OK now.