1 / 8

Bookkeeping and Tag Database

This meeting aims to define a strategy for the bookkeeping and tag database, focusing on the development of TagCollections, specialized collections of event tags with links to the event data. The meeting will also explore possibilities for a single database for everything or a hybrid system with various technologies.

tiller
Télécharger la présentation

Bookkeeping and Tag Database

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. Bookkeeping and Tag Database Define a strategy Program of Work Meeting, June 28-19, 2000 P. Mato, CERN P. Mato, CERN

  2. Event DataSet RunParam ProdParam Run MCRun TagCollection Data structures above Event Data • Entities identified • DataSet collection of events • Run a sub-type of DataSet • MCRun a sub-type of DataSet • TagCollection a collection of event tags with a link to the event. • An event can only be in one DataSet • An event can be associated to many TagCollections * * * * P. Mato, CERN

  3. Connection to GAUDI • The EventSelector is in charge of performing the selection based on a given criteria • Today: Filename, Tape number, JobId, First event, Number of events, etc. • Tomorrow: Complex queries to tag and dataset databases • The EventSelector returns a pointer (iterator) to the Event header. • This pointer is used to get the various event objects by the PersistencySvc selection criteria event iterator Event Selector DataSets TagCollections P. Mato, CERN

  4. TagCollection • The idea is to create specialized (LHCb general or private) collections of event tags with a pointer to the event head location dataSet dataSet Event dataSet trType visE muCand eCand XID Event trType visE muCand eCand XID Tag Collection trType visE muCand eCand XID Event trType visE muCand eCand XID Event few 100’s bytes P. Mato, CERN

  5. Event DataSet RunParam ProdParam Run MCRun TagCollection Current Status Not existing * * * Current Bookkeeping Database Sicb Files (tapes) * P. Mato, CERN

  6. Event DataSet RunParam ProdParam Run MCRun TagCollection Possibility A Single database for everything (Objectivity?, Oracle?) • Very attractive • single technology • full navigability • integrity and consistency • Advocated by RD45 (CMS) • Not very successful with Objectivity • Several federations • import/export databases • database catalog management * * * * P. Mato, CERN

  7. Event DataSet RunParam ProdParam Run MCRun TagCollection Possibility B • Hybrid system • Various technologies • Expertise required • Advocated by ROOT • (excluding TagCollection) • Very powerful queries to the event tags are possible • Fits well with the GAUDI architecture DB with TagCollections and DataSets * * * Event Data Files * P. Mato, CERN

  8. Proposal • Strategy: Study A and B • Develop TagCollection • Using standard N-tuples (PAW or ROOT based) • Using a relational Database (Oracle based) • Extent current EventSelector to include sophisticated queries to TagCollections • Performance comparisons between A and B P. Mato, CERN

More Related