Tags:
view all tags
<!-- keep this as a security measure: #uncomment if the subject should only be modifiable by the listed groups # * Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup,Main.CMSAdminGroup # * Set ALLOWTOPICRENAME = Main.TWikiAdminGroup,Main.CMSAdminGroup #uncomment this if you want the page only be viewable by the listed groups # * Set ALLOWTOPICVIEW = Main.TWikiAdminGroup,Main.CMSAdminGroup,Main.CMSAdminReaderGroup --> %TOC% ---+ How to work in a CMS environment ---++ Setting up the CMS environment by /cvmfs =/cvmfs= is a technology developed at CERN to easily distribute the CMSSW releases around the world ; wherever a CMS user will work he/she will find the same =/cvmfs= mount point with exactly the same files and directories ; a =/cvmfs= technical presentation can be found [[https://indico.fnal.gov/getFile.py/access?contribId=11&sessionId=4&resId=1&materialId=slides&confId=5610][here]] but the average CMS user can safely skip its implementation details and simply use it as a standard directory.</br> To use =/cvmfs= at PSI T3 you'll need to activate the basic Grid environment by: <pre> $ source /swshare/psit3/etc/profile.d/cms_ui_env.sh # for bash $ source /swshare/psit3/etc/profile.d/cms_ui_env.csh # for tcsh / csh </pre> Assuming executed the previous =source=, the following session shows an example about how to use on a SL6 =t3ui*= server the release %ORANGE%CMSSW_5_3_21%ENDCOLOR% compiled for %BLUE%slc6_amd64_gcc472%ENDCOLOR% and hosted in =/cvmfs= : <pre> $ source /swshare/psit3/etc/profile.d/cms_ui_env.sh $ echo $VO_CMS_SW_DIR /cvmfs/cms.cern.ch $ ls $VO_CMS_SW_DIR ... slc5_amd64_gcc434 %BLUE%slc6_amd64_gcc472%ENDCOLOR% slc5_amd64_gcc461 slc6_amd64_gcc480 slc5_amd64_gcc462 slc6_amd64_gcc481 slc5_amd64_gcc470 slc6_amd64_gcc490 slc5_amd64_gcc472 slc6_amd64_gcc491 %GREEN%cmsset_default.csh%ENDCOLOR% %GREEN%cmsset_default.sh%ENDCOLOR% crab3 slc5_amd64_gcc481 slc6_mic_gcc481 SITECONF ... $ cd $VO_CMS_SW_DIR/%BLUE%slc6_amd64_gcc472%ENDCOLOR%/cms/cmssw/%ORANGE%CMSSW_5_3_21%ENDCOLOR% %BLACK%# the next source might take some seconds to complete since /cvmfs is a cached network filesystem and its local cache might be empty or outdated.%ENDCOLOR% $ source $VO_CMS_SW_DIR/%GREEN%cmsset_default.sh%ENDCOLOR% $ cmsenv $ which cmsRun /cvmfs/cms.cern.ch/%BLUE%slc6_amd64_gcc472/%ENDCOLOR%cms/cmssw/%ORANGE%CMSSW_5_3_21%ENDCOLOR%/bin/%BLUE%slc6_amd64_gcc472%ENDCOLOR%/cmsRun </pre> ---++ The CMS Environment and IPython There is a *conflict* between the default IPython version %BLUE%0.13.2%ENDCOLOR% installed on each SL6 =t3ui1*= server and the older IPython version %ORANGE%0.10%ENDCOLOR% offered by CMSSW ; to switch between them use the var =IPYTHONDIR=, two different ~/.ipython dirs and a %GREEN%symbolic link%ENDCOLOR%:</br>%TWISTY% <pre> [mmasciov@t3ui17] ~$ mv .ipython %BLUE%.ipython-0.13.2%ENDCOLOR% [mmasciov@t3ui17] ~$ which ipython /swshare/cms/slc6_amd64_gcc481/cms/cmssw-patch/CMSSW_7_0_6_patch3/external/slc6_amd64_gcc481/bin/ipython [mmasciov@t3ui17] ~$ ipython ********************************************************************** Welcome to IPython. I will try to create a personal configuration directory where you can customize many aspects of IPython's functionality in: /shome/mmasciov/.ipython Initializing from configuration: /swshare/cms/slc6_amd64_gcc481/external/py2-ipython/%ORANGE%0.10%ENDCOLOR%-cms/lib/python2.7/site-packages/IPython/UserConfig Successful installation! Please read the sections 'Initial Configuration' and 'Quick Tips' in the IPython manual (there are both HTML and PDF versions supplied with the distribution) to make sure that your system environment is properly configured to take advantage of IPython's features. Important note: the configuration system has changed! The old system is still in place, but its setting may be partly overridden by the settings in "~/.ipython/ipy_user_conf.py" config file. Please take a look at the file if some of the new settings bother you. Please press <RETURN> to start IPython. ********************************************************************** Python 2.7.3 (default, Oct 19 2013, 18:04:33) Type "copyright", "credits" or "license" for more information. %ORANGE%IPython 0.10%ENDCOLOR% -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object'. ?object also works, ?? prints more. In [1]: exit() Do you really want to exit ([y]/n)? y [mmasciov@t3ui17] ~$ mv .ipython %ORANGE%.ipython-0.10%ENDCOLOR% # by default we want to use %BLUE%.ipython-0.13.2%ENDCOLOR% so we link %GREEN%.ipython%ENDCOLOR% to %BLUE%.ipython-0.13.2%ENDCOLOR% [mmasciov@t3ui17] ~$ ln -s %BLUE%.ipython-0.13.2%ENDCOLOR% %GREEN%.ipython%ENDCOLOR% # but now we want to use the %ORANGE%ipython-0.10%ENDCOLOR% so we exploit IPYTHONDIR [mmasciov@t3ui17] ~$ export IPYTHONDIR=~/.%ORANGE%ipython-0.10%ENDCOLOR% [mmasciov@t3ui17] ~$ ipython Python 2.7.3 (default, Oct 19 2013, 18:04:33) Type "copyright", "credits" or "license" for more information. %ORANGE%IPython 0.10%ENDCOLOR% -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object'. ?object also works, ?? prints more. In [1]: </pre>%ENDTWISTY% ---++ How to access your CERN AFS account You need to obtain an AFS token from the CERN server. Execute <pre> kinit YourCERNAFSName@CERN.CH aklog cern.ch </pre> You can test whether you have a valid token using the =tokens= command <pre> tokens Tokens held by the Cache Manager: User's (AFS ID 1234) tokens for afs@cern.ch [Expires Nov 7 16:11] User's (AFS ID 5432) tokens for afs@psi.ch [Expires Nov 7 10:26] </pre> If you want to use this Kerberos ticket also for password-less login into =lxplus= you'll need * create a forwardable ticket <pre> kinit -f YourCERNAFSName@CERN.CH </pre> * add the following section to your SSH configuration (=~.ssh/config=) <pre> host lxplus* GSSAPIAuthentication yes GSSAPIDelegateCredentials yes </pre> For more information about Kerberos also have a look at the [[http://linux.web.cern.ch/linux/docs/kerberos-access.shtml][CERN Kerberos access page]]. %ICON{warning}% You can use AFS for copying files between PSI and CERN, but *do not use AFS for running on software installed at CERN*, e.g. in a CMSSW environment spawned by a CERN AFS based grid/cms installation. This will create a lot of traffic, and such jobs will fail on the worker nodes for firewall reasons!!! ---++ How to use =/afs/cern.ch/sw/lcg/app/releases/ROOT= All the ROOT versions are available on =/afs/cern.ch/sw/lcg/app/releases/ROOT= ; [[https://root.cern.ch/drupal/content/production-version-534][here how to set up your shell environment for using /afs ROOT v5.34]] </br></br> You might define an alias to quickly set up your shell : <pre>alias ROOT_5.34.26='. /afs/cern.ch/sw/lcg/external/gcc/4.8/x86_64-slc6/setup.sh && . /afs/cern.ch/sw/lcg/app/releases/ROOT/5.34.26/x86_64-slc6-gcc48-opt/root/bin/thisroot.sh'</pre> ---++ How to use =/swshare/ROOT= ( old, but still working ) *Old, but still working* </br> ROOT versions locally installed at T3: * =/swshare/ROOT/root_v5.34.18_slc5_amd64= it's compiled for Python 2.4 that's the default Python release on SL5 ( old ) * =/swshare/ROOT/root_v5.34.18_slc5_amd64_py26_pythia6= has been compiled for Python 2.6 that's also available on SL5 as =python26= ( old ) * =/swshare/ROOT/root_v5.34.18_slc6_amd64_py26_pythia6= it's compiled for Python 2.6 that's the default Python release on SL6 ( the T3 is SL6 based, probably this is the version you'll use ) You can activate =/swshare/ROOT/root_v5.34.18_slc5_amd64(_py26_pythia6)= by: <verbatim> cd /swshare/ROOT/root_v5.34.18_slc5_amd64(_py26) source bin/thisroot.(c)sh </verbatim> Do the same for =/swshare/ROOT/root_v5.34.18_slc6_amd64= </br> </br> ---+ OLD DOC ---++ Setting up the CMS environment by /swshare *13-11-2014 - This is the old and deprecated way to run CMSSW at PSI T3* Like in the =/cvmfs= case you'll need to activate the basic Grid environment by: <pre> $ source /swshare/psit3/etc/profile.d/cms_ui_env.sh # for bash $ source /swshare/psit3/etc/profile.d/cms_ui_env.csh # for tcsh / csh </pre> *but*, both interactively or in a batch job, you'll have to override the variable =VO_CMS_SW_DIR= since the default value is nowadays =/cvmfs/cms.cern.ch= : <pre> $ export VO_CMS_SW_DIR=/swshare/cms # for bash $ setenv VO_CMS_SW_DIR /swshare/cms # for tcsh / csh </pre> the [[HowToSubmitJobs#a_generic_job_script][SGE job template]] has been updated to cover the =/swshare/cms= case, please have a look to it.</br> Then: <pre> source $VO_CMS_SW_DIR/cmsset_default.sh # for bash source $VO_CMS_SW_DIR/cmsset_default.csh # for tcsh / csh </pre> This will make =scram= and other CMS commands available; CMSSW is installed under =$VO_CMS_SW_DIR=. Some additional packages (e.g. *CRAB*) are located in the directory above =$VO_CMS_SW_DIR/..=. </br></br> *Be aware that no new CMSSW releases will be installed in =/swshare/cms= so please migrate to [[HowToWorkInCmsEnv#Setting_up_the_CMS_environment_b][/cvmfs]]* ---++ How to access the CERN CVS server You need to specially authenticate against the CERN CVS server. This can be done either by <strike>kerberos4,</strike> kerberos5 or by SSH. <strike>Kerberos is the most convenient solution.</strike> ---+++ Using SSH Using SSH, set up CVSROOT: <pre> export CVSROOT=':ext:isscvs.cern.ch:/cvs_server/repositories/CMSSW' export CVS_RSH=ssh </pre> and then, when you issue CVS commands, you'll be asked for your CERN password. This should be the fastest method. An example CVS command is: <pre> cvs co -r V00-02-02 QCDAnalysis/UEAnalysis </pre> ---+++ Using Kerberos If you want to use Kerberos authentication, you need to obtain a Kerberos5 ticket before you can use the CVS commands. Execute the following <pre> kinit YourCERNAFSName@CERN.CH #all letters in @CERN.CH are uppercase! </pre> and set CVSROOT: <pre> export CVSROOT=':gserver:cmscvs.cern.ch:/cvs_server/repositories/CMSSW' </pre>
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r34
|
r31
<
r30
<
r29
<
r28
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r29 - 2015-03-15
-
FabioMartinelli
CmsTier3
Log In
CmsTier3 Web
Create New Topic
Index
Search
Changes
Notifications
Statistics
Preferences
User Pages
Main Page
Policies
Monitoring Storage Space
Monitoring Slurm Usage
Physics Groups
Steering Board Meetings
Admin Pages
AdminArea
Cluster Specs
Home
Site map
CmsTier3 web
LCGTier2 web
PhaseC web
Main web
Sandbox web
TWiki web
CmsTier3 Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback