Brief Athena installation instruction

Suppose, you will actually work with two releases at least (12.0.8 and 13.0.40 below).
 
 0. Suppose you already have Pacman installed.
 
 1. First choose version what you are going to install (12.0.8 below,
    but see releases status)
    and change to installation directory (software/) :

    cd software
    mkdir 12.0.8
    cd 12.0.8

 2. Copy file trusted.caches to installation directory
    (or you will be asked many times for cofirmation to use each one).

 3. Install it (+KV -- with Kit Verification) :

    	yes | pacman -allow tar-overwrite -get am-CERN:12.0.8+KV

    [On 3 GHz PC it took me 4.5 hours to complete, 7.5 GB disk space.]


 4. Check there file setup.csh (or setup.sh) - it should contain info
    only about newly installed version (12.0.8 in the example).

 5. Run 

	source ./setup.csh

 6. Now create working directories in your Home area :

	cd
 	mkdir -p cmthome/12.0.8
 	mkdir -p cmthome/13.0.40
 	mkdir -p testarea/12.0.8
 	mkdir -p testarea/13.0.40

 7. Run 
	source $ATLAS_ROOT/CMT/v1r19/mgr/setup.csh  (or setup.sh)

    to set up some CMT env. variables.

 8. Prepare your working directory :

        cd cmthome/12.0.8/
	cp /data1/atlas/software/12.0.8/cmtsite/requirements .

In "requirements" I added lines like these :
  
  macro ATLAS_TEST_AREA ${HOME}/testarea 
  apply_tag setup
  apply_tag projectArea
  apply_tag simpleTest
  
  and commented out line
  #VR: apply_tag noTest

  File "requirements" your may take here, but rename it.

 9. Run 
  	cmt config

10. After that kill the terminal window and log back in and run 
  	
	source $ATLAS_ROOT/../work/cmthome/setup.csh -tag=12.0.8,32

  	[I do source /data1/atlas/work/cmthome/setup.csh -tag=12.0.8,32]
	
11. If you would try to install right now UserAnalysis : 

	cd ~/testarea/12.0.8/
	cmt co -r UserAnalysis-00-09-10 PhysicsAnalysis/AnalysisCommon/UserAnalysis

    you probably will get error message like this :
cvs [checkout aborted]: kerberos authentication failed: You have no tickets cached
 
[ For sysadmin only :
12. In this case you have to set up "klogin" access to CERN :

    As "root" copy to /etc/ from LXPLUS files "krb.realms krb.conf krb5.conf"
    and start "klogin" system service.
    
    Or you may edit those files, prepending following lines to them :
    
    krb.realms :
.EXAMPLE.COM	EXAMPLE.COM
CERN.CH		CERN.CH
.cern.ch	CERN.CH

    krb.conf :
CERN.CH
#This file is maintained via ncm-krb4clt
CERN.CH afsdb1.cern.ch
CERN.CH afsdb2.cern.ch
CERN.CH afsdb3.cern.ch

    krb5.conf you may take here.
]

13. To get access to CERN CVS repository you should run "kinit" (replace "vrud" by your login name) :

	/usr/kerberos/bin/kinit -4 vrud@CERN.CH

Password for vrud@CERN.CH:	<=== provide your CERN password
        
 	[Package "krb5-workstation" must be installed!]

14. Now set up CMT :

	source $ATLAS_ROOT/../work/cmthome/setup.csh -tag=12.0.8,32

15. Run

	cd ../testarea/12.0.8/
	cmt co PhysicsAnalysis/AnalysisCommon/UserAnalysis
	[or, if you know preferred release, give it as an option :
	 cmt co -r UserAnalysis-00-09-10 PhysicsAnalysis/AnalysisCommon/UserAnalysis]

 You will see :

# ================= working on package UserAnalysis version UserAnalysis-00-10-07 (At head)  path PhysicsAnalysis/AnalysisCommon in /data1/atlas/work/testarea/12.0.8/PhysicsAnalysis/AnalysisCommon/UserAnalysis
  # get top files
cvs update: [08:37:39] waiting for cvsadmin's lock in /atlascvs/CVSROOT
cvs update: [08:38:09] obtained lock in /atlascvs/CVSROOT
cvs update: Updating .
Creating setup scripts.
Creating cleanup scripts.
run directory already installed
...

See installed structure :

 ls -F PhysicsAnalysis/AnalysisCommon/UserAnalysis/
ChangeLog*  cmt/  CVS/  doc/  python/  Root/  run/  share/  src/  UserAnalysis/

        cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/
	source setup.csh 
 	gmake

        cd ../run
        get_files PDGTABLE.MeV jobOptions.pythia.py 
        athena jobOptions.pythia.py >& Log.jobOptions.pythia.py.Jan22_1 

    User Analysis Package instruction see here.

   PROBLEM : no access yet to 'get_tag' command, what means that '...AtlasCore/2.0.7/Tools/Scripts/share/'
             is NOT in the PATH after above setups ??
             But maybe that is normal for non AFS installation?
-----------------------------------------------

16. When you will start to work next time, run setups in following order :

	cd /data1/atlas/work
	source ../software/12.0.8/setup.csh
	cd testarea/12.0.8/
	source $ATLAS_ROOT/../work/cmthome/setup.csh -tag=12.0.8

    To exclude first two lines, just add to your .login these lines :

# add Atlas env-s :
source /data1/atlas/software/12.0.8/setup.csh	

    After that next time just do  :

	source $ATLAS_ROOT/../work/cmthome/setup.csh -tag=12.0.8
	cd /data1/atlas/work/testarea/12.0.8/



Original by July 06, 2007.
Last modified on Feb 05, 2008.