How to read conditions data - PoolDBESSource

Complete: 3


Parameters and public interfaces described in this page are compatible wit CMSSW_2_0_0 and higher. For using older release versions, please read older version of the page.

Configuration Parameters for PoolDBESSource

name type description default allowed
connect string database connection string None POOLORA connection string format
globaltag untracked string None global tag format "TREE::node"
appendToDataLabel untracked string None  
BlobStreamerName untracked string "DefaultBlobStreamingService" "TBufferBlobStreamingService"
toGet VPSet vector of {record,tag} pairs to identify the data to retrieve None  

DBParameters(see below) named Parameter Set common database connection parameters default values provided by the common .cfi file  

Named Parameter Set DBParameters sets the connection parameters. The default values are provided by the framework in the following files CondCore/DBCommon/data/CondDBCommon.cfi or CondCore/DBCommon/data/CondDBSetup.cfi.

The common practice is to include one of the above default .cfi in job configuration and replace the parameters you want to customise.

Parameters in named parameter set DBParameters

name type description default allowed
authenticationPath untracked string directory path to the authentication file "." current dir empty string or a valid path. If empty string, environment variables CORAL_AUTH_USER, CORAL_AUTH_PASSWORD should be set by the user
messageLevel untracked int32 verbosity level 0 0(Error),1(Warning), 2(Info), 3(Debug)
enableConnectionSharing untracked bool connection sharing switch true true, false
connectionTimeOut untracked int32 connection timeout value 600(sec)  
connectionRetrialPeriod untracked int32 connection retry time interval 30(sec)  
connectionRetrialTimeOut untracked int32 connection retry timeout 180(sec)  

Note: parameter DBParameters.authenticationPath should point to the location of your authentication.xml. For example, at CERN one of the locations on AFS is "/afs/".


Suppose following the example in How to write conditions data, you created and now In PedestalsAnalyzer, you ask the EventSetup for
    edm::ESHandle<Pedestals> pPeds;
    const Pedestals* myped=pPeds.product();
    //analyze myped

process MYTEST = {
     include "CondCore/DBCommon/data/CondDBCommon.cfi"
     replace CondDBCommon.connect = "sqlite_file:test.db"
     replace CondDBCommon.DBParameters.messageLevel = 3
        es_source = PoolDBESSource {
          using CondDBCommon
          VPSet toGet = {
              {string record = "PedestalsRcd"
               string tag = "mytest"
               } } 
   source = EmptyIOVSource {
          string timetype = "runnumber"
          untracked uint32 firstRun = 1
        untracked uint32 lastRun = 10
          uint32 interval = 1
   module prod = PedestalsAnalyzer{}
     path p = { prod }

Auxiliary modules

  • EmptyIOVSource

     source = EmptyIOVSource {
         string timetype = "runnumber"
         untracked uint32 firstRun = 1
       untracked uint32 lastRun = 10
         uint32 interval = 1

Review Status

Reviewer/Editor and date Comments
ZhenXie - 16 Feb 2007 page author
JennyWilliams - 03 Apr 2007 moved page into swguide
ZhenXie - 14 Apr 2008 major update
Responsible: ZhenXie
Last reviewed by: Reviewer
Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2014-03-09 - AndreaVenturi

    • 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