Setup of software in the experimental software area CMS

The installations are launched centrally as grid jobs by the CMS administrators.

External Information

• twiki page on the distribution policy
• central page about deployed CMSSW versions
• List of deprecated releases
• List of anounced releases

CMS requests that any special setup that a user needs to do, and which departs from standard CMS policy, be recorded on this page of the CERN wiki.

Installations triggered by central CMS operations

This is the normal way to go. The installation job will be launched by a CMS software manager and the job will get mapped to the cmssgm user on the site. Our CE is configured in a way that only certain nodes have write access to the software area. The batch scheduler is configured to run these jobs just on these nodes!

After successful installation the job will also make the necessary adjustments so that information about the software is published in the grid information system.

Local Site Configuration Files

here

Testing the software setup

Test for correct setting of environment

Ideally you do the following test on a worker node. But it should also work on a user interface (but maybe you need to set the VO_CMS_SW_DIR variable correctly).

Part of the older CMMSW is only available in SLC3 compatibility mode on our SLC4 machines. This requires an additional setting before doing any of the steps below:

$> # only do this for getting the older CMSSW versions
$> export SCRAM_ARCH=slc3_ia32_gcc323

A grid job will source the local CMS environment as a first step:

$> . $VO_CMS_SW_DIR/cmsset_default.sh
Loading site local CMS environment

after that, the scramv1 command should be available. SCRAM does the software building and configuration/environment management for CMS.

You should be able to list the available CMS software packages with

$> scramv1 list

The following sets up a local software development area and runs a sample job for one of the CMSSW versions. Pick one of the version from the list produced by the scramv1 command above.

CMSSW_VERSION=CMSSW_1_2_3

scramv1 project CMSSW $CMSSW_VERSION      # creates a local project work area
cd $CMSSW_VERSION/src
export CVSROOT=:pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW
cvs login   # anonymous access to CMS CVS requires password "98passwd"
cvs co -r $CMSSW_VERSION SimG4Core/Application/test
cd SimG4Core/Application/test
eval `scramv1 runtime -sh`   # this sets up the local environment needed by the app in that directory
cmsRun -p runP.cfg   # runs a standard test

-- DerekFeichtinger - 29 Jan 2008