Difference: RunningAtlasInGlasgow (2 vs. 3)

Revision 32009-11-11 - ThomasDoherty

Line: 1 to 1
 -- ThomasDoherty - 2009-11-03

Running ATLAS Software at Glasgow

Line: 93 to 93
  point to - 
 /data/atlas07/chrisc/CSC-AOD/trig1_misal1_mc12.006855.AcerMCttbb_QCD.recon.AOD.v12000605_tid011597/AOD.011597._00002.pool.root.1
Added:
>
>		at the line starting "ServiceMgr.EventSelector.InputCollections = " in the JO.
 (16) And finally run the JO: 

athena.py AnalysisSkeleton _topOptions.py > AnalysisSkeleton.log
Line: 108 to 110
  (1) Log in to a ppe machine - example: ssh ppepc17
Changed:
<
<		(2) Make a test area if you haven't already and change into this directory - example: cd atlas
>
>		(2) Make a test area if you haven't already and change into this directory - example: 
cd atlas
 
Changed:
<
<		(3) Make a directory specific to the v15 release you are going to use - example: ANALYSISSSL5-V15.3.0.1
>
>		(3) Make a directory specific to the v15 release you are going to use - example: 
ANALYSISSSL5-V15.3.0.1
 
Changed:
<
<		and again make a further directory within this one - example mkdir ANALYSISSSL5-V15.3.0./15.3.0.1
>
>		and again make a further directory within this one - example: 

mkdir ANALYSISSSL5-V15.3.0./15.3.0.1
  (4) Now we want to set up CMT and your requirements file directory - if you wish create a requirement file
Line: 128 to 134
 
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
Changed:
<
<
(6) Now source the set up script for the CMT version you wnat to use - example
>
>
(6) Now source the set up script for the CMT version you want to use - example
 
Changed:
<
<		source /data/atlasb04/software15/CMT/v1r20p20090520/mgr/setup.sh
>
>
source /data/atlasb04/software15/CMT/v1r20p20090520/mgr/setup.sh
 
Changed:
<
<		(7) As your requirements file is new and specific to v15 you must create the CMT setup scripts for it - by: cmt config
>
>		(7) As your requirements file is new and specific to v15 you must create the CMT setup scripts for it - by: 
cmt config
 
Changed:
<
<		(8) Now you can set up CMT for your specific release (v15.3.0.1) by sourcing the setup file like this:
>
>		(8) Now you can set up CMT for your specific release (example v15.3.0.1) by sourcing the setup file like this:
 
Changed:
<
<		source setup.sh -tag=ANALYSISSSL5-V15.3.0.1,32,15.3.0.1,runtime,AtlasProduction
>
>
source setup.sh -tag=ANALYSISSSL5-V15.3.0.1,32,15.3.0.1,runtime,AtlasProduction
  (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-

Changed:
<
<		more /data/atlasb04/software15/AtlasAnalysis/15.3.0/PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/version.cmt
>
>
more /data/atlasb04/software15/AtlasAnalysis/15.3.0/PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt/version.cmt
 
Changed:
<
<		(11) Now check out the package (in $TEST/ANALYSISSL4-v12.0.6/12.0.6) by:
cmt co -r UserAnalysis-00-09-10 PhysicsAnalysis/AnalysisCommon/UserAnalysis
>
>		so in this case it is UserAnalysis-00-13-17
 
Changed:
<
<		(13) when successfully checked out we now want to compile this code (after changes are made) by:
>
>		(11) Now check out the package (in $TEST/ANALYSISSSL5-V15.3.0.1/15.3.0.1) by: 
cmt co -r UserAnalysis-00-13-17 PhysicsAnalysis/AnalysisCommon/UserAnalysis

(12) Now you must set up SVN/CVS here in GLasgow. Normally it takes the form of: 

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

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

 
Changed:
<
<		(a) cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt
>
>		(a) 
cd PhysicsAnalysis/AnalysisCommon/UserAnalysis/cmt
 
Changed:
<
<		(b) source setup.sh
>
>		(b) 
source setup.sh
 
Changed:
<
<		(c) cmt bro gmake
>
>		(c) 
cmt bro gmake
  (14) Now we want to run Athena with a basic JO. This means you need to change into your run directory (cd ../run)
Changed:
<
<		and then fetch the JO by: get_files AnalysisSkeleton _topOptions.py
>
>		and then fetch the JO by: 
get_files AnalysisSkeleton_topOptions.py
  (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

Added:
>
>		at the line starting "ServiceMgr.EventSelector.InputCollections = " in the JO.
 (16) And finally run the JO:
Changed:
<
<		athena.py AnalysisSkeleton _topOptions.py > AnalysisSkeleton.log
>
>
athena.py AnalysisSkeleton_topOptions.py

and append '> 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... 

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

and then run Athena

View topic | History: r7 < r6 < r5 < r4 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback