1 / 14

Conditions DB in LHCb

Conditions DB in LHCb. LCG Conditions DB Workshop 8-9 December 2003 P. Mato / CERN. Contents. Scope of Conditions DB Project History Requirements Integration with Gaudi Current Status Summary. Conditions DB: Scope.

zelig
Download Presentation

Conditions DB in LHCb

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conditions DB in LHCb LCG Conditions DB Workshop 8-9 December 2003 P. Mato / CERN

  2. Contents • Scope of Conditions DB • Project History • Requirements • Integration with Gaudi • Current Status • Summary Conditions DB in LHCb

  3. Conditions DB: Scope • Everything that is needed in terms of detector conditions by “Offline” Event Data Processing Applications • It is not intended for troubleshooting the detector and DAQ system • Event Data can not be reconstructed/analyzed without it • Time validity period > 5 minutes • World-wide access • Distributed world-wide data analysis • GRID-aware (replica, closest available copy, etc.) • Multi-platform and very long-life time • Data analysis will be done in many different platforms • Conditions data will need to be available for many years Conditions DB in LHCb

  4. History and Status • Started several years ago • Identified the needs (one of the ingredients of the Gaudi architecture) • Defined interfaces in collaboration with other LHC experiments and IT/DB • Prototypes • Developed prototype of integration in Framework • Tested Oracle implementation • Hit by manpower limitations • No work done for more than one year • Identified as one of the major critical items in recent Manpower Review • In the processes of identifying new resources Conditions DB in LHCb

  5. Version Time VDET alignment HCAL calibration RICH pressure ECAL temperature t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 Data Item Time = T Condition Database Requirements • Storage/Retrieval of time depend data items • Versioning • Tagging • Ability to extract slices of data • Not intrusive and as much as possible transparent for the algorithms Tag1 definition Version Time Conditions DB in LHCb

  6. Remote Site Remote Site CalibrationApplication Worker Node CalibrationApplication Rec/Anal Application Algorithm Algorithm Cond DB slice Mgr Tools Mgmt Tools Cond DB Cond DB replica Online DB master copy The Big Picture Conditions DB in LHCb

  7. Remote Site Remote Site CalibrationApplication Worker Node CalibrationApplication Rec/Anal Application Algorithm Algorithm Cond DB Mgr Tools slice Mgmt Tools Cond DB Cond DB Online DB replica master copy Splitting the Work • Common: • Database implementations (more than one) • Tools for management, data browsing, replication, slicing, import/export • Deployment of DB services • LHCb specific: • Data contents • Interface to Algorithms (Gaudi framework) • Data sources: calibration programs, online system, etc. Conditions DB in LHCb

  8. Material Solid DataObject PVolume LVolume Element Mixture Solid Solid ReadOut SolidBox Isotope MuonStation DetectorElement Calibration DetDesc Class Diagram (simplified) Association resolved on demand Hierarchy * IDetectorElement IGeometryInfo GeometryInfo ILVolume IReadOut * IMaterial ISolid IPVolume ICalibration * * Specific detector description questions from algorithms Detector Description Geometry Material Conditions DB in LHCb

  9. Detector Data Service Persistency Service Condition Service Ask for Object Check presence Ask creation Ask for data Retrieve them from Database Algorithm Lvolume Abstract interface Lvolume Cnv Lvolume Lvolume Condition Db Geometry Retrieve pointer Gaudi Interface to Conditions Db • Emphasis on the data retrieval functionality • One new service was defined : ConditionSvc • Independent from data content, only deals with data retrieval depending on time, version and/or tag • Fully transparent for the user Conditions DB in LHCb

  10. Current Prototype (1) • We store “verbose” XML in the condition database, exactly as it is in the XML files for geometry • We use references to point an object in the condition database, with a new protocol called “conddb” <catalog name="Hcal"> <conditionref href="conddb:/CONDDB/SlowControl/Hcal#scHcal"/> </catalog> • The retrieval in C++ is absolutely identical, no distinction between condition data and regular data SmartDataPtr<DetectorElement> lhcb(detSvc(), "Structure/LHCb"); if (!sc.isSuccess()) return StatusCode::FAILURE; Condition* alLHCb = lhcb->alignment()->condition(); Conditions DB in LHCb

  11. Current Prototype (2) • Note the “new” part of the Detector Element API virtual IAlignment* alignment (); virtual ICalibration* calibration(); virtual IReadOut* readOut (); virtual ISlowControl* slowControl(); virtual IFastControl* fastControl(); • All these interfaces inherits from IConditionInfo class IConditionInfo ... virtual IDetectorElement* detElem() const = 0; virtual const std::string conditionName() const = 0; virtual Condition* condition() = 0; • Condition is an object which handles a set of parameters, exactly like DetectorElement. It can also be extended in the same ways (including <specific> tag and converters) Conditions DB in LHCb

  12. Current Prototype (3) • The way to populate the condition database today is manual • Look at the examples in the Ex/DetCondExample package StatusCode sc = serviceLocator()->service (“ConditionsDBCnvSvc", cdbSvc ); IConditionsDBGate* cdbGate = cdbSvc->conditionsDBGate(); ICondDBMgr* cdbMgr = cdbGate->condDBManager(); ICondDBDataAccess* cdbDatAcc = cdbMgr->getCondDBDataAccess(); cdbMgr->startUpdate(); ICondDBObject* cObj = CondDBObjFactory::createCondDBObject (since, till, “**** XML CODE ****”, “Comment”) cdbDatAcc->storeCondDBObject ("/CONDDB/SlowControl/LHCb/scLHCb", cObj); CondDBObjFactory::destroyCondDBObject(cObj); cdbMgr->commit(); Conditions DB in LHCb

  13. What we are missing? • A port of the database to other technologies (MySQL,…) • To be able to run in “disconnected mode” • Similarly as the POOL file catalogue • A tool to populate / browse / edit the condition database. • A tool to make slices of the condition database that you may store locally on your laptop or send to your computing node in a production environment • Data to try out the current implementation in real conditions • Develop coherent calibration/alignment procedures among LHCb sub-detectors • Someone who has time to supervise all this activity Conditions DB in LHCb

  14. Summary • Stated long ago to work on Conditions DB but without continuity due to manpower reductions • Prototypes to evaluate current ideas exist • Not yet used in production • The LHCb core software team aims • To facilitate the task for Algorithm writers (framework should take care of most of the work) • To encourage common developments between sub-detectors in the areas like alignment, calibration, connection to online system, etc. • The Conditions DB common project is an opportunity of sharing the work • LHCb can not afford to do it alone • We have enough work with the LHCb specifics Conditions DB in LHCb

More Related