SLHC jet alogrithms

Robyn's usercode area:

http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/UserCode/rlucas/SLHCjetSimulations/

Code can be checked out with the CVS command:

cvs co -d DIRECTORY_NAME Usercode/rlucas/HIGHER_DIRECTORIES

For example to check out specific directories in a Usercode area:

cvs co -d CalCaloProducer UserCode/rlucas/SLHCjetSimulations

CVS Prerequisties

If checking out code from a machine outside lxplus, the following commands must first be used:

export CVSROOT=MY_CERN_USERNAME@cmscvs.cern.ch:/cvs_server/repositories/CMSSW

A kerberos 5 ticket must also be acquired for authentication (note: case sensitive CERN.CH):

kinit -5 -A myCernUsername@CERN.CH

Produce Jet Collections

Use the following commands to build a valid CMSSW area and checkout the necessary files for the jet producer:

SCRAM_ARCH=slc5_amd64_gcc462; export SCRAM_ARCH
cmsrel CMSSW_6_0_1_PostLS1v2_patch4
cd CMSSW_6_0_1_PostLS1v2_patch4/src/

cvs co -r calCenJet7Feb2013 SLHCUpgradeSimulations/L1CaloTrigger
cvs co -r L1CaloBranch SimDataFormats/SLHC

And build with the command below. Note -j40 with submit the make command to 40 processes, redude this to -j4 when not building on lxplus

scram b -j40

Analysis code

The root files produced can be analyzed with the following recipe:

cmsrel CMSSW_6_0_1_PostLS1v2_patch4
cd CMSSW_6_0_1_PostLS1v2_patch4/src
cmsenv 

cvs co -r calCenJet7Feb2013 SLHCUpgradeSimulations/L1CaloTrigger
cvs co -r L1CaloBranch SimDataFormats/SLHC 

mkdir AnalyseUpgradeJets 
cvs co -d AnalyseUpgradeJets/ UserCode/rlucas/SLHCjetSimulations/AnalyseUpgradeJets/ 

And again build with scram, changing to -j4 if necessary:

scram b -j40 
cd AnalyseUpgradeJets/

To generate a ROOT file with the producer:

cmsRun ProduceJetCollections.py

CRAB Notes

The below commands apply to a CRAB folder zMuMu_v1

Create Job

The python configuration file crab.cfg can be used to create a new job to be processed on the GRID with the command:

crab -create

Submit Job

This can then be submitted to the GRID with the command:

crab -submit -c zMuMu_v1

Checking Job Status

First the latest information of the Job progress should be obtained by -getoutput

crab -getoutput -c zMuMu_v1
Then the status of the current jobs can be obtained by the -status command
crab -status -c zMuMu_v1

Which will output a table of the Job status

crab:  Checking the status of all jobs: please wait
crab:  
ID    END STATUS            ACTION       ExeExitCode JobExitCode E_HOST
----- --- ----------------- ------------  ---------- ----------- ---------
1     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
2     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
3     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
4     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
5     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
6     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
7     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
8     Y   Aborted           Aborted                              lcgce03.phy.bris.ac.uk
9     Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk
10    Y   Retrieved         Cleared       0          0           lcgce03.phy.bris.ac.uk

crab:  ExitCodes Summary
 >>>>>>>>> 9 Jobs with Wrapper Exit Code : 0 
    List of jobs: 1-7,9-10 
   See https://twiki.cern.ch/twiki/bin/view/CMS/JobExitCodes for Exit Code meaning

crab:   10 Total Jobs 
 >>>>>>>>> 1 Jobs Aborted
   You can resubmit them specifying JOB numbers: crab -resubmit <List of jobs>
   List of jobs: 8 
 >>>>>>>>> 9 Jobs Retrieved 
   List of jobs Retrieved: 1-7,9-10 
The ExitCode gives details if a Job is successful (ExitCode = 0) or fails, in which case the reason for failure can be found from the link: JobExitCodes.

A more detailed output can be obtained from the -report command

crab -report -c zMuMu_v1

Resubmitting Failed Jobs

If a Job does fail it must be resubmitted, this can be achieved with the -resubmit command. This command takes as an argument the range of jobs that are to be resubmitted which may be comma seperated and contain ranges. For example to resubmit Jobs 2,5,6,7,10 we may use the command

crab -resubmit 2,5-7,10 -c zMuMu_v1

Killing Jobs

The status of current jobs can be easily checked with the web interfaceCMS Dashboard. Note that crab -getoutput must first be called to ensure the data is up to date.

Twiki CRAB Tutorial

-- MarkBaber - 25-Feb-2012

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2013-02-22 - MarkBaber
 
    • 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-2021 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