RunningAtlasInGlasgow < ATLAS

-- Main.ThomasDoherty - 2009-11-03

*This is mostly deprecated information - releases should be setup and used from [[LocalPPEAccounts][cvmfs]] instead. The conditions data setup is probably still useful though* -- %USERSIG{GraemeStewart - 2014-01-14}%

---+ Running ATLAS Software at Glasgow

---++ Using AtlasSetup at Glasgow

The three key lines are:

export ATLAS_ROOT=/data/atlasb04/software16_slc5_gcc43 export

AtlasSetup =${ATLAS_ROOT}/AtlasSetup

alias asetup='source ${AtlasSetup}/scripts/asetup.sh'

and then you can set up as normal for example:

asetup AtlasPhysics,16.6.5.5.1

---++ Setting up for real data

It is necessary to point to the conditions pool file catalogues. To do this using afs set the following environment variable:

export ATLAS_POOLCOND_PATH=/afs/cern.ch/atlas/conditions/poolcond/catalogue

It is also necessary to point to the nearest frontier client - in our case at Glasgow this is:

export FRONTIER_SERVER="(serverurl=<a href="http://lcgft-atlas.gridpp.rl.ac.uk:3128/frontierATLAS%29%28serverurl=http://oratest02.pic.es:3128/pic-frontier%29%28proxyurl=http://nat005.gla.scotgrid.ac.uk:3128%29%28proxyurl=http://fal-pygrid-45.lancs.ac.uk:3128" target="_blank">http://lcgft-atlas.gridpp.rl.ac.uk:3128/frontierATLAS)(serverurl=http://oratest02.pic.es:3128/pic-frontier)(proxyurl=http://nat005.gla.scotgrid.ac.uk:3128)(proxyurl=http://fal-pygrid-45.lancs.ac.uk:3128</a>)"

---++ Installation locations

The locations for the Atlas releases are
<pre>   /data/atlasb01/software for release      12.X.Y
   /data/atlasb01/software for release      13.X.Y  
  (/data/atlas04/software is backup)   

   /data/atlasb02/software for release      14.X.Y
  (/data/atlas04/software14 is backup)

  /data/atlasb04/software15 for release     15.X.Y

</pre>

NOTE: When setting up CMT for your release - if you have an SL5 machine - make sure you use the tag '32' otherwise Python will be set up incorrectly. For example:

source setup.sh -tag=ANALYSISSSL5-V15.3.0.1,<strong>32</strong>,15.3.0.1,runtime,AtlasProduction

---++ Setting up v12 locally
---+++ How to set up an analysis skeleton on an sl4 PPE machine for v12

(1) Log in to the ppe machine - example: ssh ppepc17

(2) Make a test area if you haven't already and change into this directory - example:
<verbatim>cd atlas</verbatim>

(3) Make a directory specific to the v12 release you are going to use - example:
<verbatim>mkdir ANALYSISSL4-v12.0.6</verbatim>

and again make a further directory within this one - example
<verbatim>mkdir ANALYSISSL4-v12.0.6/12.0.6</verbatim>

(4) Now we want to set up CMT and your requirements file directory - if you wish create a requirement file

specifically for v12 and store it in a directory that indicates this - example make a directory and change into ../cmthome-v12

(5) The requirements file should look something like this:

###########################################

set CMTSITE STANDALONE<br />set SITEROOT /data/atlasb01/software<br /><br />macro ATLAS_TEST_AREA "${HOME}/atlas/CSC-eventview" \<br /> ANALYSISSL4-v12.0.6 "${HOME}/atlas/ANALYSISSL4-v12.0.6"\<br />macro ATLAS_DIST_AREA ${SITEROOT}<br />macro ATLAS_GROUP_AREA "/data/atlasb01/software/EVGroupArea/Stable"<br />apply_tag projectArea<br />macro SITE_PROJECT_AREA ${SITEROOT}<br />macro EXTERNAL_PROJECT_AREA ${SITEROOT}<br />apply_tag opt<br />apply_tag projectTest<br />use AtlasLogin AtlasLogin -* $(ATLAS_DIST_AREA)<br />set CMTCONFIG i686-slc3-gcc323-opt<br /><br />macro DBRel "2.8" \<br /> 12.0.31 "2.8" \<br /> 12.0.4 "3.0.1" \<br /> 12.0.5 "3.1.1" \<br /> 12.0.6 "3.2.1" \<br /> 12.3.0 "2.9.1" \<br /> 12.5.0 "3.2.1"<br />set DBRELEASE_INSTALLED ${DBRel}

# set DBRELEASE_INSTALLED 3.2.1<br /><br />path TEST ""<br />path_append TEST "$(TestArea)"<br /><br />macro home_dir "${HOME}"<br />path_remove CMTPATH "${home_dir}"<br />path_prepend CMTPATH "${TestArea}"

######################################################

<br />where you have added the location of the directory "ANALYSISSL4-v12.0.6" to it so you can set it up as a cmt tag.

<br />(6) Now source the set up script for the CMT version you want to use - example

<verbatim>source /data/atlasb01/software/CMT/v1r19/mgr/setup.sh</verbatim>

(7) As your requirements file is new and specific to v12 you must create the CMT setup scripts for it - by:
<verbatim> cmt config</verbatim>

(8) Now you can set up CMT for your specific release (v12.0.6) by sourcing the setup file like this:

<verbatim>source setup.sh -tag=ANALYSISSL4-v12.0.6,12.0.6</verbatim>

and

<verbatim>source /data/atlasb01/software/AtlasProduction/12.0.6/AtlasProductionRunTime/cmt/setup.sh</verbatim>

(9) Now we want to check out the UserAnalysis package for this release to do this first change into your testarea (cd $TEST)

(10) To find out the specific package version needed fro this release try this-

<verbatim>more /data/atlasb01/software/AtlasAnalysis/2.0.6/PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/version.cmt</verbatim>

(11) As v12 was not migrated to the svn repository it still lies on the old CVS server - so we need to set up CVS (just for v12 - note although this is strange behaviour expect to enter your password up to 6 times) by:

<verbatim>export CVSROOT=":ext:isscvs.cern.ch:/local/reps/atlas/"

export CVS_RSH="ssh"</verbatim>

(12) Now check out the package (in $TEST/ANALYSISSL4-v12.0.6/12.0.6) by:

<verbatim>cmt co -r UserAnalysis-00-09-10 PhysicsAnalysis/AnalysisCommon/UserAnalysis</verbatim>

(13) when successfully checked out we now want to compile this code (after changes are made) by:

(a)
<verbatim> cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt</verbatim>

(b)
<verbatim> source setup.sh</verbatim>

(c)
<verbatim>cmt bro gmake</verbatim>

(14) Now we want to run Athena with a basic JO. This means you need to change into your run directory (cd ../run)

and then fetch the JO by:
<verbatim> get_files AnalysisSkeleton _topOptions.py</verbatim>

(15) We want to change the JO to point to the input AOD that we want to run our Analysis on for example:

point to -
<verbatim> /data/atlas07/chrisc/CSC-AOD/trig1_misal1_mc12.006855.AcerMCttbb_QCD.recon.AOD.v12000605_tid011597/AOD.011597._00002.pool.root.1</verbatim>

at the line starting "ServiceMgr.EventSelector.InputCollections = " in the JO.

(16) And finally run the JO:

<verbatim>athena.py AnalysisSkeleton _topOptions.py &gt; AnalysisSkeleton.log</verbatim>

---++ Setting up v14 Locally

Follow the instructions in the link below to setup up v14 Locally ( Note and issue with python setup is currently being fixed for SL5 machines).

[[http://ppewww.physics.gla.ac.uk/~chrisc/logs/v14-steps.txt][Release 14.2.25.5]]

---++ Setting up v15 Locally
---+++ How to set up an analysis skeleton for v15

(1) Log in to a ppe machine - example: ssh ppepc17

(2) Make a test area if you haven't already and change into this directory - example:
<verbatim>cd atlas</verbatim>

(3) Make a directory specific to the v15 release you are going to use - example:
<verbatim>ANALYSISSSL5-V15.3.0.1</verbatim>

and again make a further directory within this one - example:

<verbatim>mkdir ANALYSISSSL5-V15.3.0./15.3.0.1</verbatim>

(4) Now we want to set up CMT and your requirements file directory - if you wish create a requirement file

specifically for v15 and store it in a directory that indicates this - example make a directory and change into ../cmthome-v15

(5) The requirements file should look something like this:

###########################################

set CMTSITE STANDALONE<br />set SITEROOT /data/atlasb04/software15<br />macro ATLAS_DIST_AREA /data/atlasb04/software15<br />macro ATLAS_TEST_AREA ${HOME}/Test-14-0-0 \<br /> ANALYSISSSL4-V15.3.0.1 ${HOME}/atlas/ANALYSISSSL4-V15.3.0.1\<br /> ANALYSISSSL5-V15.3.0.1 ${HOME}/atlas/ANALYSISSSL5-V15.3.0.1<br />#macro ATLAS_TEST_AREA ${HOME}/atlas/AtlfastCorrectorsTEST<br />apply_tag projectArea<br />macro SITE_PROJECT_AREA ${SITEROOT}<br />macro EXTERNAL_PROJECT_AREA ${SITEROOT}<br />apply_tag simpleTest<br />use AtlasLogin AtlasLogin -* $(ATLAS_DIST_AREA)<br />set CMTCONFIG i686-slc4-gcc34-opt<br />set DBRELEASE_INSTALLED 3.1.1<br />path_remove CMTPATH "$(TestArea)"<br />path_prepend CMTPATH "$(TestArea)"<br />path TEST ""<br />path_append TEST "$(TestArea)"

###########################################

<br />where you have added the location of the directory "ANALYSISSSL5-V15.3.0.1" to it so it can be used as a cmt tag

<br />(6) Now source the set up script for the CMT version you want to use - example

<verbatim>source /data/atlasb04/software15/CMT/v1r20p20090520/mgr/setup.sh</verbatim>

(7) As your requirements file is new and specific to v15 you must create the CMT setup scripts for it - by:
<verbatim>cmt config</verbatim>

(8) Now you can set up CMT for your specific release (example v15.3.0.1) by sourcing the setup file like this:

<verbatim>source setup.sh -tag=ANALYSISSSL5-V15.3.0.1,32,15.3.0.1,runtime,AtlasProduction</verbatim>

(9) Now we want to check out the UserAnalysis package for this release to do this first change into your testarea (cd $TEST)

(10) To find out the specific package version needed fro this release try this-

<verbatim>more /data/atlasb04/software15/AtlasAnalysis/15.3.0/PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/version.cmt</verbatim>

so in this case it is UserAnalysis -00-13-17

(11) Now check out the package (in $TEST/ANALYSISSSL5-V15.3.0.1/15.3.0.1) by:
<verbatim>cmt co -r UserAnalysis-00-13-17 PhysicsAnalysis/AnalysisCommon/UserAnalysis</verbatim>

(12) Now you must set up SVN/CVS here in GLasgow. Normally it takes the form of:
<verbatim>export SVNROOT=svn+ssh://USERNAME@svn.cern.ch/reps/atlasoff</verbatim>

where USERNAME is your CERN lxplus username. Example:
<verbatim>export SVNROOT=svn+ssh://tdoherty@svn.cern.ch/reps/atlasoff
unset CVSROOT</verbatim>

(13) when successfully checked out we now want to compile this code (after your code changes are made) by:

(a)
<verbatim>cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt</verbatim>

(b)
<verbatim>source setup.sh</verbatim>

(c)
<verbatim>cmt bro gmake</verbatim>

(14) Now we want to run Athena with a basic JO. This means you need to change into your run directory (cd ../run)

and then fetch the JO by:
<verbatim>get_files AnalysisSkeleton_topOptions.py</verbatim>

(15) We want to change the JO to point to the input AOD that we want to run our Analysis on for example:

point to - /data/atlas07/chrisc/CSC-AOD/trig1_misal1_mc12.006855.AcerMCttbb_QCD.recon.AOD.v12000605_tid011597/AOD.011597._00002.pool.root.1

at the line starting "ServiceMgr.EventSelector.InputCollections = " in the JO.

(16) And finally run the JO:

<verbatim>athena.py AnalysisSkeleton_topOptions.py</verbatim>

and append '&gt; AnalysisSkeleton.log' to this if you want to write the output to a log

(17) NOTE: If you find that your code changes have not been picked up when you run Athena - sometimes you have to compile, THEN LOG OUT AND RESTART YOUR SESSION. SET UP THE ENV again...

<verbatim>i.e. NEW WINDOW
cd cmthome-v15
source setup.sh -tag=ANALYSISSSL5-V15.3.0.1,32,15.3.0.1,runtime,AtlasProduction
cd $TEST
cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt
source setup.sh
cd ../run</verbatim>

and then run Athena
This topic: ATLAS > RunningAtlasInGlasgow
Topic revision: r7 - 2014-01-14 - GraemeStewart