ComputingCMSSWBenchmarks < Main

---+ The configuration

I wish that no one needs to do this anymore. With DAS it can be really painful. I didn't really find the LFN there, but rather in my email, when I had to SCP it to a remote server in the past. It is :

/store/data/Run2012C/SingleMu/RAW/v1/000/201/624/FC7C9690-C0ED-E111-AE93-003048D2BC52.root

So once you get the Configuration/DataProcessing from here :

https://github.com/cms-sw/cmssw/tree/CMSSW_5_3_X

As CVS is dead, then run this :

<verbatim>
[lxplus443] /tmp/CMSSW_5_3_8/src > Configuration/DataProcessing/test/RunPromptReco.py --scenario pp --global-tag GR_E_V37::All --lfn /store/data/Run2012C/SingleMu/RAW/v1/000/201/624/FC7C9690-C0ED-E111-AE93-003048D2BC52.root
Retrieved Scenario: pp
Using Global Tag: GR_E_V37::All
magnetic field option forced to: AutoFromDBCurrent
RAW2DIGI
L1Reco
RECO
ALCAPRODUCER:@allForPrompt
DQM
ENDJOB
Now do:
cmsRun -e RunPromptRecoCfg.py
[lxplus443] /tmp/CMSSW_5_3_8/src >
</verbatim>

---+ Priceless tricks

---++ Frontier access

What I had to do once, is to benchmark a node in a remote network where only 22 outbound and 80 outbound connections were allowed. Tough. Frontier was a huge, hidden problem. Here's the priceless advice for this, from HLT/Framework experts :

https://hypernews.cern.ch/HyperNews/CMS/get/edmFramework/3150.html

---++ Global Tag

Looks like this is a huge potential pitfall. Hard to find and hard to guess. [[https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideFrontierConditions#Global_Tags_for_pre_2015_data_ex][This]] is a page that supposedly lists the right ones.

-- Main.samir - 2014-08-11

This topic: Main > ComputingCMSSWBenchmarks
Topic revision: r3 - 2014-08-13 - samir

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback