User Software and Computing
Computing Environment Setup
General CMS Software Environment
Platform specific setup
Application runtime environment
Accessing CERN CVS server
References
General CMS Software Environment
The CMS software environment for csh and tcsh users is set by sourcing the environment setup script.
In tcsh, csh:
source /uscmst1/prod/sw/cms/cshrc [option]
In bash, sh:
. /uscmst1/prod/sw/cms/shrc [option]
This will set general CMS software environment variables, extend the user's $PATH to include CMS specific utilities and tools, and define aliases used in the CMS software projects.
User can set one of the environments by choosing the corresponding argument to the environment setup script. NOTE: if environment is already set, sourcing a script will not change the environment. A warning will be printed out **).
Currently available environments:
| Environment option |
$CMS_PATH | Software available |
| prod | /uscmst1/prod/sw/cms | Sets the environment for CMS production software installed on the /uscmst1/prod filesystem. Available on any desktop or node at Fermilab with the /uscmst1/prod filesystem mounted. |
| nightly | /uscms_data/d1/cms_admin/ | Sets the environment for CMSSW software built nightly with debug options and prereleases built with debug options. Available to any desktop with the /uscms and /uscms_data/d1 filesystems mounted. |
*) The default for the environment can be set by defining the environment variable $CMS_ENV_DOMAIN prior sourcing the environment setup script.
**) No output is produced in non-interactive mode.
Platform specific environment
SCRAM version V0_20_0 does not distinguish between RedHat 7.3 and Scientific Linux platforms. All UAF nodes have Scientific Linux 3 installed. Therefore on the UAF you have to explicitly specify the correct architecture either using '-arch slc3_ia32_gcc323' option to scram, or by setting the environment variable SCRAM_ARCH to the same value, e.g.:
setenv SCRAM_ARCH slc3_ia32_gcc323
SCRAM version V1_0_0 and higher automatically chooses the correct architecture. You only need to redefine the architecture if you want to change the default. For example, to access the SL4 releases:
setenv SCRAM_ARCH slc4_ia32_gcc345
On nodes with Athlon64 or Opteron processors SCRAM version V1_0_0 sets the architecture automatically to slc4_amd64_gcc345. However the CMS software installed at Fermilab is compiled for the slc3_ia32_gcc323 and slc4_ia32_gcc345 architectures. To get the CMS software you need to set:
setenv SCRAM_ARCH slc3_ia32_gcc323
or
setenv SCRAM_ARCH slc4_ia32_gcc345
Application runtime environment
Runtime environment for applications is generated by scramv1 runtime -csh or scramv1 runtime -sh command, executed in the area associated with a particular version of product. It may be development area created by a user, or a public release area. Note, that output differs between the versions, and the runtime environment itself is not set automatically. To set it, evaluate the command above using the shell eval function:
eval `scramv1 runtime -sh` (or -csh)
Accessing CERN CVS server
Accessing the CERN CVS server requires the correct authentication and the setting the correct CVSROOT variable. For information on how to do this please consult this page.
References
For further references about using scram commands please consult SCRAM documentation . For questions concerning this page and CMS software environment at FNAL send email to: Patrick Gartung , Natalia Ratnikova or helpdesk@fnal.gov
