ATLAS Software: Difference between revisions
m (1 revision imported) |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
=== Interactive machines at LHEP === | === Interactive machines at LHEP === | ||
ui01.lhep.unibe.ch | |||
ui02.lhep.unibe.ch | |||
ui03.lhep.unibe.ch | |||
=== Basic SVN === | === Basic SVN === | ||
Line 12: | Line 12: | ||
=== LCG Grid Access === | === LCG Grid Access === | ||
To setup the lcg grid environment, | To setup the lcg grid environment, setup CVMFS first : | ||
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase | |||
source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh | |||
alias asetup='source $AtlasSetup/scripts/asetup.sh' | |||
= | Then type: | ||
lsetup emi | |||
=== Prepare and check your grid certificate === | === Prepare and check your grid certificate === | ||
To prepare your grid certificate, follow the following tutorial (you can adapt the procedure to our interactive nodes): | To prepare your grid certificate, follow the following tutorial (you can adapt the procedure to our interactive nodes): | ||
https://twiki.cern.ch/twiki/bin/ | https://twiki.cern.ch/twiki/bin/view/AtlasComputing/WorkBook | ||
https://twiki.cern.ch/twiki/bin/view/AtlasComputing/WorkBookStartingGrid (Preparing your certificate) | |||
To verify the expiry date of your grid certificate installed in the .globus subdir of your home directory (on teh interactive nodes and/or lxplus): | To verify the expiry date of your grid certificate installed in the .globus subdir of your home directory (on teh interactive nodes and/or lxplus): | ||
Line 35: | Line 31: | ||
=== Use | === Use Rucio === | ||
To be able to use | To be able to use the rucio commands, you need to setup CVMFS first: | ||
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase | |||
source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh | |||
alias asetup='source $AtlasSetup/scripts/asetup.sh' | |||
Then type | |||
lsetup rucio | |||
=== Athena setup with CVMFS === | === Athena setup with CVMFS === | ||
CVMFS is a caching file system which hosts all athena releases and conditions data flat files. It was initially developed for the Cern-VM [https://twiki.cern.ch/twiki/bin/viewauth/Atlas/CernVM] Virtualization Software. | |||
<h4> Athena Setup </h4> | <h4> Athena Setup </h4> | ||
To setup a particular release and testarea use the following commands and replace 17.0.2 and /path/to/my/testarea appropriately: | To setup a particular release and testarea use the following commands and replace 17.0.2 and /path/to/my/testarea appropriately: | ||
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase | |||
source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh | |||
alias asetup='source $AtlasSetup/scripts/asetup.sh' | |||
asetup 17.0.2 --testarea /path/to/my/testarea | |||
<h4> Conditions DB files </h4> | <h4> Conditions DB files </h4> | ||
Line 64: | Line 55: | ||
/cvmfs/atlas-condb.cern.ch/repo/conditions/ | /cvmfs/atlas-condb.cern.ch/repo/conditions/ | ||
Line 83: | Line 68: | ||
cd ../run | cd ../run | ||
And finally run your code calling your program (the name defined in the cmt/requirement file) | And finally run your code calling your program (the name defined in the cmt/requirement file) | ||
Latest revision as of 15:19, 23 June 2016
Interactive machines at LHEP
ui01.lhep.unibe.ch ui02.lhep.unibe.ch ui03.lhep.unibe.ch
Basic SVN
svn mkdir -m “Add OQMaps dir" http://svn.lhep.unibe.ch/subv/atlas/SUSY2011/cutflow/OQMaps svn co http://svn.lhep.unibe.ch/subv/atlas/SUSY2011/cutflow/OQMaps svn add * # All files you have in OQMaps. Directories must be created like above. svn ci "Add OQMaps”
LCG Grid Access
To setup the lcg grid environment, setup CVMFS first :
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh alias asetup='source $AtlasSetup/scripts/asetup.sh'
Then type:
lsetup emi
Prepare and check your grid certificate
To prepare your grid certificate, follow the following tutorial (you can adapt the procedure to our interactive nodes):
https://twiki.cern.ch/twiki/bin/view/AtlasComputing/WorkBook https://twiki.cern.ch/twiki/bin/view/AtlasComputing/WorkBookStartingGrid (Preparing your certificate)
To verify the expiry date of your grid certificate installed in the .globus subdir of your home directory (on teh interactive nodes and/or lxplus):
cd ~/.globus openssl x509 -in usercert.pem -noout -enddate
Follow this link[1] for a summary of useful openssl commands.
Use Rucio
To be able to use the rucio commands, you need to setup CVMFS first:
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh alias asetup='source $AtlasSetup/scripts/asetup.sh'
Then type
lsetup rucio
Athena setup with CVMFS
CVMFS is a caching file system which hosts all athena releases and conditions data flat files. It was initially developed for the Cern-VM [2] Virtualization Software.
Athena Setup
To setup a particular release and testarea use the following commands and replace 17.0.2 and /path/to/my/testarea appropriately:
export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh alias asetup='source $AtlasSetup/scripts/asetup.sh' asetup 17.0.2 --testarea /path/to/my/testarea
Conditions DB files
The conditions DB flat files can be found in:
/cvmfs/atlas-condb.cern.ch/repo/conditions/
How to use ROOT libraries from gcc
CINT, the compiler included within ROOT, is not fully reliable from my point of view just for at least two reasons. First, it allows some "bad code writing" hard to debug once you change your ROOT release. Second, CINT, as python, is not a real compiler but just interpret your code for each event. So, if your code becomes sophisticated (kinematic fits,...) CINT spend much more time to interpret your code for each event than running on the event. But, you can use ROOT as libraries from gcc, in a CMT environment in the following :
source /terabig/atlsoft/LocalSoft/tools/config/setup.sh
Then, go in your package/cmt directory (an example can be found here [3]) This package, written for the SUSY/Trigger analysis as been documented using Doxygen. The documentation can be found here[4](page reachable only from unibe.ch domain)
cmt config source setup.sh gmake (or make) cd ../run And finally run your code calling your program (the name defined in the cmt/requirement file)