Page currently under construction


This pages describes instructions how to access work with Athena and tau software.


https://indico.cern.ch/category/3l11/ --> ATLAS Reconstruction /TF4 , usually every Tuesday at 4pm


  1. hn-atlas-TauWG@cernNOSPAMPLEASE.ch --> official Tau WorkingGroup Mailingliste
  2. atlas-cp-tau-coresoft@cernNOSPAMPLEASE.ch --> mailinglist for all tau software related issues
  3. atlas-sw-tf4@cernNOSPAMPLEASE.ch --> TF4 taskforce: xAOD migration, but currently used for many expert question around release 19
  4. hn-atlas-recoIntegration@cernNOSPAMPLEASE.ch --> the official Athena reconstruction expert list
  5. atlas-sw-tagapprove@cernNOSPAMPLEASE.ch --> the official tag approval mailing list. Need to request new tags into (non-dev) releases
  6. hn-atlas-offlineSWDevelopment@cernNOSPAMPLEASE.ch --> expert help for Athena development (more specific to Athena development than the list hn-atlas-offlineSWHelp@cernNOSPAMPLEASE.ch, which is a general one and mostly used for questions about how to write analysis software)
  7. hn-atlas-SWDevelopersAnnounce@cernNOSPAMPLEASE.ch --> no help, but just a announce list for Workshops, Conferences, Tutorials, server/url changes etc.
  8. hn-atlas-releaseKitAnnounce@cernNOSPAMPLEASE.ch --> new Athena releases and there availability at AFS and Grid are announced here.
  9. hn-atlas-offlineSWHelp@cernNOSPAMPLEASE.ch --> I don't follow this list regulary. People having questions about tauRec (not so many) putting hopefully one of the developers or convenors in cc
  10. atlas-sw-future-technologies-forum@cernNOSPAMPLEASE.ch and hn-atlas-cernCompAnnounce@cernNOSPAMPLEASE.ch --> not related to taus but interesting if you like software



  1. SVN
  2. Doxygen entry
  3. Flow Chart
  4. File overview

other tau packages

  1. https://svnweb.cern.ch/trac/atlasoff/browser/PhysicsAnalysis/TauID/TauDiscriminant[SVN tauDiscriminant]]
  2. SVN xAODTau - the new xAOD tau Event Data Model
  3. SVN xAODTauAthenaPool
  4. SVN AOD->xAOD converter
  5. SVN tauEvent - old tau Event Data Model (run1)

instructions for tau software

  1. Tau xAOD instructions (pretty much up-to-date)
  2. general instructions on how to run tau software (run1, Athena release 17 related)
  3. expert instructions, but not up-to-date (run1, Athena release 17 related)

usefull links for Athena

  1. code browser for Athena
  2. AMI --> TagCollector
  3. TagCollectorInAtlas twiki
  4. AtlasComputing
  5. AtlasSetup reference (the asetup command)
  6. Release overview - tells you what releases are available and provide usefull informations about them
  7. NICOS - the ATLAS Nightly Test System
  8. RTT - ATLAS RunTimeTest entry page
  9. AthenaScripts: Tool collection for Athena - still usefull for r19, but perhaps not all already migrated
  10. SoftwareTutorialxAODAnalysisInAthena
  11. see which Athena Version is installed on the GRID sites


asetup devval,rel_2,here

check what version of a package is included

cmt show versions Reconstruction/tauRec 
cmt show versions Reconstruction/xAOD/xAODTau
cmt show versions PhysicsAnalysis/TauID/TauDiscriminant

checkout, trunk

cmt co Reconstruction/tauRec  
checkout specific tag
 cmt co -r tauRec-xx-yy-zz Reconstruction/tauRec  


cd Reconstruction/tauRec/cmt
source setup.sh
cmt make
source setup.sh 

basic test, the basic and easiest test is TODO: Reco_trf is not supported in r19, use Reco_tf

mkdir run
cd run
Reco_trf.py outputESDFile=outESD.pool.root outputAODFile=outAOD.pool.root inputRDOFile=../RDO.784554._001055.pool.root.1 beamType=collisions autoConfiguration=everything --ignoreerrors=True maxEvents=20 &> athena_log & 

Athena releases

Athena comes in many releases mostly numbered like How to read this numbers: 17 -> major version 12.2 -> branching (17.1 series is used for Trigger (called P1-releases), 17.2 series is used for Reconstruction (data+MC) (called T0 releases) 17.2.8 -> minor changes -> patched version

4-digit releases are called AtlasProduction releases and mostly used for all kind of Reconstruction (so up to AOD) 5-digit releases are called AtlasPhysics (or physics-cache, or pcache), like and are used for D3PD Production or other stuff.

The releases and their different calls are coded in the eXXX,sXXX,rXXX,pXXX tags of the datasets. You can look them up here using AMI.


Releases are build from nightly-releases or so-called validation release. Every new tag goes first into a validation release and after running (compilation + tests) successfully it will go into the full release. For P1/T0 releases (like 17.2.8.x ) you have to request such new tags via the atlas-sw-tagapprove@cernNOSPAMPLEASE.ch mailing list with CC'ing the corresponding coordinators. But this is only important for bugfixes or if a new feature need to be backported to a T0 release.

For developments there is a special release, called "dev". This is an alias for the next major release or branching release. Currently "dev" means 19.1.2. The validation release of "dev" is called "devval".

most important side containing a complete overview is: http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/global/

Most of the nightlies exist in 7 incorporations, called rel_0,1,2,3,4,5,6 for the different days of the week, starting with Sunday (rel_0). So if you setup a release with > asetup, RELEASENUMBER,rel_2
for example, this will be stable for exactly 1 week. After that rel_2 will be overwritten with the next build.

For a large development cycle a Production release is good to use, because the dev nightlies are sometimes unstable. But after everything was tested locally you need to bring in major changes in to the dev-release. For this you need to setup dev or devval via > asetup devval,rel_2,here
> asetup dev,rel_2,here

To figure out which release is stable take a look at http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/global/ pick the release you want, e.g. 19.X.0-VAL (devval) http://atlas-computing.web.cern.ch/atlas-computing/links/distDirectory/nightlies/global/index19.X.0-VAL.html and you see that everything is Green which is a good sign. For tauRec compilation at least up to AtlasReconstruction everything should be green. If you want to run some tests with that release AtlasAnalysis, Offline and Production should be green. Depending on the environment somebody like to use only x86_64-slc6-gcc47-opt or the ggc48 version x86_64-slc6-gcc47-opt (64bit, standard when doing asetup) are important.

x86_64-slc6-gcc47-dbg is build with debug symbols, while i686-slc6-gcc47-opt is a 32bit build. Both of them should only be used for special problems, when you are sure you need these releases.

-- FelixFriedrich - 18 Jul 2014

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2014-07-25 - FelixFriedrich
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback