Instructions for producing sqlite files with L1 fake conditions

Setup CMSSW area

For CMSSW_3_1_0_pre7 and later:

cmsrel CMSSW_X_Y_Z
cd CMSSW_X_Y_Z/src
cvs co CondTools/L1Trigger
scramv1 b
cd CondTools/L1Trigger/test
cmsenv

Sqlite file with IDEAL conditions

cmsRun L1ConfigWritePayloadDummy_cfg.py
cmsRun L1ConfigWriteIOVDummy_cfg.py

Output file is called l1config.db.

Sqlite file with STARTUP conditions

cmsRun L1ConfigWritePayloadDummy_cfg.py tagBase=STARTUP startup=1
cmsRun L1ConfigWriteIOVDummy_cfg.py tagBase=STARTUP

Output file is called l1config.db.

Reading fake conditions in cmsRun

Insert the following python snippet in your configuration file, with tagBase set to IDEAL or STARTUP as appropriate. No need to remove the Global Tag; it will be overridden by the sqlite file.

from CondTools.L1Trigger.L1CondDBSource_cff import initCondDBSource
initCondDBSource( process,
    inputDBConnect = 'sqlite_file:l1config.db',
    tagBase = 'IDEAL_OR_STARTUP',
    includeAllTags = True )

-- WernerSun - 24 Jun 2009

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2011-02-13 - WernerSun
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

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