Test simple CMSSW batch submission on local files/SE

Setup CMSSW environment

• source the CMS environment

  source /swshare/cms/cmsset_default.sh

• prepare to run CMSSW

  cd CMSSW_Version/src; eval `scramv1 runtime -(c)sh`

  or

  cmsenv

Run CMSSW interactively on a file stored on t3se01.psi.ch

• To run CMSSW interactively on a file stored on the t3se01.psi.ch, modify the "PoolSource" parameters in the CMSSW config file as follows

  source = PoolSource {
      untracked vstring fileNames = {
        'dcap://t3se01.psi.ch:22125/pnfs/psi.ch/cms/catalog/store/user/zlchen/FCF4A854-8705-DD11-ADAE-00304856292C.root'
      }
      untracked int32 maxEvents = 10
    }
  
       

Submit CMSSW jobs to SGE

• For SGE, Batch jobs are shell scripts. Job submission is telling SGE to execute a shell script. You normally start your program from within that script. You don't need to create old-school job description files since you can talk with SGE from within the job script in case you need. Lines starting with #$ are interpreted by SGE. Below is a sample job script for submitting CMSSW job to SGE:

  #!/bin/bash
  #
  #$ -cwd
  #$ -j y
  #$ -S /bin/bash
  #
  date
  hostname
  pwd
  source /swshare/cms/cmsset_default.sh 
  cmsenv
  cmsRun MyConfig.cfg
     

Submit it with command

qsub test.job

. In the job script, the lines starting with a #$ are SGE commands. Above, -cwd tells sge to cd to the directory job has been submitted when it starts running(e.g. your cmssw project directory), "-j y" is to transfer the current environment variable state to the shell starting the job and -S tells which shell to dispatch the job with.

-- ZhilingChen - 04 Sep 2008