Adding and using new crab parameters

  • Modify the appropriate file under /data/hc/external/ganga/install/HEAD/python/GangaCMS/Lib/ConfParams

  • Set the values of the new parameters in one of the following places:
    • A template file under /data/hc/apps/cms/inputfiles/templates/, e.g.
          Job (
             inputdata = CRABDataset (
                ...
                role = 'production',
                ...
             )
             ...
          ) 
    • In Extraargs in a test template, e.g. -o[USER_CFG]tasktype=hcprivate

Installing a new version of CMSSW

$ ssh gangarbt@vocms06
$ cd /data/hc/external/cms/crab/scripts
$ CMSSW_REL=CMSSW_<version>
Modify CMSSW_generic.sh if needed to set the correct SCRAM_ARCH
$ cd /data/hc/external/cms/crab
$ bash
$ export SCRAM_ARCH=slc5_amd64_gcc462 (or newer, as required)
$ source /data/hc/external/cms/crab/scripts/cmsset_default.sh
$ CMSSW_REL=CMSSW_<version>
$ scram project CMSSW ${CMSSW_REL}
$ cd ${CMSSW_REL}/src
$ eval `scram runtime -sh`
$ addpkg ElectroWeakAnalysis/ZEE
$ cvs co -d HammerCloudTests COMP/INTEGRATION/HammerCloud/HammerCloudTests
(it might be necessary to add the option -r ${CMSSW_REL}, ask Leonardo Sala)
$ scram b -c ; scram b
(check for compilation errors)
$ cp HammerCloudTests/TestJobs/test/*.py /data/hc/external/cms/crab/configurations
NOTE: be very careful not to overwrite a used configuration with a newer version not backward-compatible!! If you do so, current tests will start to fail. Rename accordingly the new and/or the old version to keep them both.

Definitions in the HC web interface Go to the administrative interface and log in Add an input type for CMSSW_<version> Add a user code for any new configuration (compare with those in /data/hc/external/cms/crab/configurations) Add two test options with these values:

  • Name: CMSSW_<version> (production)
  • Config: -v CMSSW_<version> -r production
  • Submit: -o[CMSSW]CMSSW_VERSION=$CMSSW_VERSION -o[CMSSW]CMSSW_SETUP=$HCDIR/external/cms/crab/scripts
  • Report: -o[CMSSW]CMSSW_VERSION=$CMSSW_VERSION -o[CMSSW]CMSSW_SETUP=$HCDIR/external/cms/crab/scripts
and:
  • Name: CMSSW_<version> (no role)
  • Config: -v CMSSW_<version> -r user
  • Submit: -o[CMSSW]CMSSW_VERSION=$CMSSW_VERSION -o[CMSSW]CMSSW_SETUP=$HCDIR/external/cms/crab/scripts
  • Report: -o[CMSSW]CMSSW_VERSION=$CMSSW_VERSION -o[CMSSW]CMSSW_SETUP=$HCDIR/external/cms/crab/scripts

Test that it works

Create a template with these parameters:

  • Category: stress
  • Description: Default stress - CMSSW_<version> (no role)
  • Lifetime: 0
  • Active: x
  • Jobtemplate: 10_1000.tpl
  • Usercode: MTR3.py
  • Optionfile: empty
  • Metricperm: mp2
  • Inputtype: CMSSW_<version>
  • Testoption: CMSSW_<version> (no role)
  • Gangabin: /install/ALT/bin/ganga
  • Extraargs: <none>
  • Host: use default
  • Template backends: use defaults
  • Template clouds: use defaults
  • Template sites: use defaults
  • Dspattern: use the most recent JobRobot

Create a test with these parameters:

  • Starttime: as soon as possible
  • Endttime: 24 hours after
  • Description: CMSSW_<version> test
  • Template: the previosly created one
  • Click on "Save and continue editing"
  • Test sites: Num datasets per bulk = 1, Min queue depth = 50, Max running jobs = 50, Site = one you can trust
  • Click on "Save"
  • Approve the test
  • After some time, check for errors

Use the new version for the functional tests

  • Edit the relevant templates and change as needed:
    • Usercode
    • Inputtype
    • Testoption
    • the dataset(s)
  • Go to the existing functional test pages from the main HC page and for each of them modify the end time to be a few minutes in the future (the only way to "kill" a test)

Installing a new version of CRAB

$ ssh gangarbt@vocms38
$ CRABVER=CRAB_<version>
$ cd /data/hc/external/cms/crab/CRAB
$ wget http://cmsdoc.cern.ch/cms/ccs/wm/www/Crab/Docs/$CRABVER.tgz
If the URL above returns a 404 code, one can use the following command having access to AFS:
$ cp /afs/cern.ch/cms/ccs/wm/scripts/Crab/$CRABVER.tgz .
$ tar zxf $CRABVER.tgz
$ cd $CRABVER
$ ./configure
NOTE: until further notice, patch the installed CRAB version by commenting the line:
sched_param+='MyProxyServer = "' + self.proxyServer + '";\n'
in SchedulerGlite.py to work around a WMS bug that causes very short proxies to be assigned to jobs.
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2012-07-17 - AndreaSciaba
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback