Conditions Database

1
Conditions Database

• Andrea Valassi
• Pere Mato

2
Overview of components

• Framework design issues
• The Algorithms need not talk directly to the
  CondDB.
• Within the Gaudi framework, CondDBSvc is the
  service responsible for updating the Transient
  Detector Store with data from the CondDB.
• Software responsibilities
• LHCb-related issues are CondDBSvc design and
  interface to CondDB data type specification.
• CondDB is being developed by CERN IT division.

Align
Transient detector store
3
Open issues in the design

• HOW to store/retrieve condition data
• framework design of CondDBSvc (independent of
  data type)
• synchronisation of Transient Detector Store used
  by the Algorithms
• detector data identification
• truly LHCb-specific separation of
  Align/Slow/Calib or Vdet/Ecal/Hcal/Rich...
• general to CondDB-design versioning over
  multiple validity ranges
• interface and needed functionalities/features
  for the CondDB
• general to CondDB-design, involves feedback to IT
• WHAT to store as condition data
• may be different for Alignment, Calibration,
  SlowControl...
• may vary from SubDetector to SubDetector
• uniform implementation store condition data as
  XML strings?
• also recommend a uniform description of similar
  data for all SD s

4
Interface to ITs CondDB

• Good collaboration and feedback with IT DB group
• Stefano Paoli, Dirk Duellmann
• Parallel requirement documents
• from LHCb (Pere, february 2000)
• from IT (Stefano, june 2000)
• Open design issues on functionalities and
  interface
• versioning schemas over multiple time validity
  ranges
• tag the head vs. tag any combination of data
  blocks splitting of data blocks
• browsing with global tags
• add new data blocks vs. update existing data
  blocks
• internal vs. external database management
• transaction management, concurrency issues
• support of multiple storable data types
• separation of data and meta-data

5
Data identification and versioning
6
Plans and timescales

• Work plan for CondDBSvc
• use cases and requirements from SubDetectors
• concentrate at first on one data type Alignment
• identify example of SD(s) with condition data to
  store and algorithms to use it ?
• design and integrate software in the framework,
  test on the example(s)
• iterate feedback to IT
• Plans for CondDB from IT
• current effort on collecting our requirements
• first reasonable prototype could be ready in a
  couple of months from now
• My personal plans...
• 50 on LHCb from mid-August (after coming back
  from Osaka...)
• getting started with Gaudi at first (DetDataSvc,
  DetPersSvc, XML...)
• Summing up prototyping of CondDBSvc around ?
  October to December
• or is the CondDBSvc needed for a critical
  deadline before?