Difference between revisions of "AMA in Athena 14 1 0"
Line 1: | Line 1: | ||
− | ===Setting up | + | ===Setting up ATLAS Release 14.1.0 at NIKHEF === |
Only once: | Only once: | ||
<ul> | <ul> | ||
Line 26: | Line 26: | ||
</pre> | </pre> | ||
+ | ===AtlasModularAnalysis=== | ||
+ | |||
+ | To obtain the code, do the following: | ||
in <tt>/project/atlas/users/<username>/14.1.0/PhysicsAnalysis</tt>: | in <tt>/project/atlas/users/<username>/14.1.0/PhysicsAnalysis</tt>: | ||
<pre> | <pre> | ||
Line 31: | Line 34: | ||
</pre> | </pre> | ||
− | + | ||
There are three ways of running AMA: | There are three ways of running AMA: | ||
<ul> | <ul> | ||
Line 40: | Line 43: | ||
For FDR-II: try running AMA in Athena. | For FDR-II: try running AMA in Athena. | ||
+ | |||
+ | ==== Within Athena (AMAAthena) ==== | ||
+ | |||
+ | <i>NB: All AtlasRelease (athena) compilation and runtime activities should | ||
+ | be perform only in the bash shell</i> | ||
+ | |||
+ | Starting in <tt>/project/atlas/users/<user>/14.1.0/PhysicsAnalysis</tt>: | ||
+ | <ul> | ||
+ | <li>first compile AMA | ||
+ | <pre> | ||
+ | $ cd AtlasModularAnalysis/cmt | ||
+ | $ cmt config | ||
+ | $ . setup.sh | ||
+ | $ gmake | ||
+ | </pre> | ||
+ | <li>copy AMAAthena and compile | ||
+ | <pre> | ||
+ | $ cd /project/atlas/users/<user>/14.1.0/PhysicsAnalysis | ||
+ | $ cp -r /data/atlas/users/gossie/Athena/AMAAthena . | ||
+ | $ cd AMAAthena/cmt | ||
+ | $ cmt config | ||
+ | $ . setup.sh | ||
+ | $ gmake | ||
+ | </pre> | ||
+ | </ul> | ||
+ | |||
+ | To set up the runtime environment for AMAAthena in conjuction with | ||
+ | the grid file stager do the following from a <i>clean</i> shell | ||
+ | |||
+ | <pre> | ||
+ | $ source /global/ices/lcg/current/etc/profile.d/grid_env.sh | ||
+ | $ voms-proxy-init | ||
+ | (your pass phrase goes here) | ||
+ | $ PYTHONPATH= | ||
+ | $ source $HOME/cmthome/setup.sh -tag=14.1.0,32 | ||
+ | </pre> | ||
+ | |||
+ | This specific order is required to avoid a python clash between the | ||
+ | grid middleware and the ATLAS release environment | ||
+ | |||
+ | run AMAAthena with: | ||
+ | <pre> | ||
+ | $ athena AMAAthena_jobOptions_FDR.py | ||
+ | </pre> | ||
====Standalone==== | ====Standalone==== | ||
Line 89: | Line 136: | ||
======JetCollectionCnv_p2====== | ======JetCollectionCnv_p2====== | ||
https://hypernews.cern.ch/HyperNews/Atlas/get/PATDevelopment/270/1.html | https://hypernews.cern.ch/HyperNews/Atlas/get/PATDevelopment/270/1.html | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 13:19, 6 June 2008
Setting up ATLAS Release 14.1.0 at NIKHEF
Only once:
- Create a file: $HOME/cmthome/requirements (and modify <username>)
set CMTSITE STANDALONE set SITEROOT /data/atlas/offline/14.1.0 macro ATLAS_TEST_AREA /project/atlas/users/<username> macro ATLAS_DIST_AREA ${SITEROOT} apply_tag projectArea macro SITE_PROJECT_AREA ${SITEROOT} macro EXTERNAL_PROJECT_AREA ${SITEROOT} 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/setup.sh
- $ cmt config in $HOME/cmthome
Everytime you log on:
$ source $HOME/cmthome/setup.sh -tag=14.1.0,32
AtlasModularAnalysis
To obtain the code, do the following: in /project/atlas/users/<username>/14.1.0/PhysicsAnalysis:
$ cvs -d /project/atlas/cvs/Athena co -r V00-00-04-04 AtlasModularAnalysis
There are three ways of running AMA:
- Standalone (no AODs)
- with ARA (all formats)
- in Athena (only AODs)
For FDR-II: try running AMA in Athena.
Within Athena (AMAAthena)
NB: All AtlasRelease (athena) compilation and runtime activities should be perform only in the bash shell
Starting in /project/atlas/users/<user>/14.1.0/PhysicsAnalysis:
- first compile AMA
$ cd AtlasModularAnalysis/cmt $ cmt config $ . setup.sh $ gmake
- copy AMAAthena and compile
$ cd /project/atlas/users/<user>/14.1.0/PhysicsAnalysis $ cp -r /data/atlas/users/gossie/Athena/AMAAthena . $ cd AMAAthena/cmt $ cmt config $ . setup.sh $ gmake
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/grid_env.sh $ voms-proxy-init (your pass phrase goes here) $ PYTHONPATH= $ source $HOME/cmthome/setup.sh -tag=14.1.0,32
This specific order is required to avoid a python clash between the grid middleware and the ATLAS release environment
run AMAAthena with:
$ athena AMAAthena_jobOptions_FDR.py
Standalone
$ gmake -f Makefile.Standalone amacint $ gmake -f Makefile.Standalone CSCDriver
With ARA
from kit
(no extra tags) in AtlasModularAnalysis/cmt
$ cmt config $ source setup.sh $ gmake
with recommended tags
(see also: https://twiki.cern.ch/twiki/bin/view/Atlas/AthenaROOTAccess#14_1_0 ):
- 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 setup.sh $ gmake
issues
CMT
source setup.sh in AtlasModularAnalysis/cmt directory gives crash when running AMA with ARA.
Solution: do another source setup.sh in the AthenaROOTAccess/cmt directory. Now you can run AMA with ARA without problems again.
PYTHONPATH
Sometimes ARA crashes just after initialisation. This is due to a wrongly set PYTHONPATH. To correct this:
- Copy /data/atlas/users/gossie/Athena/fix_AMA-ARA_PYTHONPATH.sh to anywhere you like
- replace <username> with your username
- $ source fix_AMA-ARA_PYTHONPATH.sh
running i686-slc4-gcc34-opt/CSCDriver.exe should be OK now.
JetCollectionCnv_p2
https://hypernews.cern.ch/HyperNews/Atlas/get/PATDevelopment/270/1.html