1 Databases in ALICE L.Betev LCG Database Deployment and Persistency Workshop Geneva, October 17, 2005.

Slides:



Advertisements
Similar presentations
March 24-28, 2003Computing for High-Energy Physics Configuration Database for BaBar On-line Rainer Bartoldus, Gregory Dubois-Felsmann, Yury Kolomensky,
Advertisements

André Augustinus ALICE Detector Control System  ALICE DCS is responsible for safe, stable and efficient operation of the experiment  Central monitoring.
Grid and CDB Janusz Martyniak, Imperial College London MICE CM37 Analysis, Software and Reconstruction.
Peter Chochula, January 31, 2006  Motivation for this meeting: Get together experts from different fields See what do we know See what is missing See.
23/04/2008VLVnT08, Toulon, FR, April 2008, M. Stavrianakou, NESTOR-NOA 1 First thoughts for KM3Net on-shore data storage and distribution Facilities VLV.
F Fermilab Database Experience in Run II Fermilab Run II Database Requirements Online databases are maintained at each experiment and are critical for.
Overview of Data Management solutions for the Control and Operation of the CERN Accelerators Database Futures Workshop, CERN June 2011 Zory Zaharieva,
Talend 5.4 Architecture Adam Pemble Talend Professional Services.
Star (Traditional) Database Tasks & MySQL 1. Database Types & Operation Issues 2. Server & Database deployments 3. Tools with MySQL 4. Data definition.
C. Aiftimiei- December 2003 ALICE NIPNE-HH Cristina Aiftimiei National Institute for Physics and Nuclear Engineering - Horia.
JCOP Workshop September 8th 1999 H.J.Burckhart 1 ATLAS DCS Organization of Detector and Controls Architecture Connection to DAQ Front-end System Practical.
HPS Online Software Discussion Jeremy McCormick, SLAC Status and Plans.
IceCube DAQ Mtg. 10,28-30 IceCube DAQ: “DOM MB to Event Builder”
Conditions DB in LHCb LCG Conditions DB Workshop 8-9 December 2003 P. Mato / CERN.
1 Alice DAQ Configuration DB
Update on Database Issues Peter Chochula DCS Workshop, June 21, 2004 Colmar.
LHC: ATLAS Experiment meeting “Conditions” data challenge Elizabeth Gallas - Oxford - August 29, 2009 XLDB3.
Databases E. Leonardi, P. Valente. Conditions DB Conditions=Dynamic parameters non-event time-varying Conditions database (CondDB) General definition:
4/5/2007Data handling and transfer in the LHCb experiment1 Data handling and transfer in the LHCb experiment RT NPSS Real Time 2007 FNAL - 4 th May 2007.
ALICE, ATLAS, CMS & LHCb joint workshop on
ATLAS Detector Description Database Vakho Tsulaia University of Pittsburgh 3D workshop, CERN 14-Dec-2004.
And Tier 3 monitoring Tier 3 Ivan Kadochnikov LIT JINR
Clara Gaspar, March 2005 LHCb Online & the Conditions DB.
The Persistency Patterns of Time Evolving Conditions for ATLAS and LCG António Amorim CFNUL- FCUL - Universidade de Lisboa A. António, Dinis.
ATLAS Data Challenges US ATLAS Physics & Computing ANL October 30th 2001 Gilbert Poulard CERN EP-ATC.
Introduction CMS database workshop 23 rd to 25 th of February 2004 Frank Glege.
Databases in CMS Conditions DB workshop 8 th /9 th December 2003 Frank Glege.
ALICE Condition DataBase Magali Gruwé CERN PH/AIP Alice Offline week May 31 st 2005.
Peter Chochula ALICE Offline Week, October 04,2005 External access to the ALICE DCS archives.
Planning and status of the Full Dress Rehearsal Latchezar Betev ALICE Offline week, Oct.12, 2007.
4 Oct 2005 / Offline week Shuttle program for gathering conditions data from external DB Boyko Yordanov 4 October 2005 ALICE Offline week.
AliRoot survey P.Hristov 11/06/2013. Offline framework  AliRoot in development since 1998  Directly based on ROOT  Used since the detector TDR’s for.
Michele de Gruttola 2008 Report: Online to Offline tool for non event data data transferring using database.
Development of the CMS Databases and Interfaces for CMS Experiment: Current Status and Future Plans D.A Oleinik, A.Sh. Petrosyan, R.N.Semenov, I.A. Filozova,
IceCube Offline Database Overview Georges Kohnen Université de Mons-Hainaut
Configuration database status report Eric van Herwijnen September 29 th 2004 work done by: Lana Abadie Felix Schmidt-Eisenlohr.
Andrea Valassi (CERN IT-DB)CHEP 2004 Poster Session (Thursday, 30 September 2004) 1 HARP DATA AND SOFTWARE MIGRATION FROM TO ORACLE Authors: A.Valassi,
The ATLAS DAQ System Online Configurations Database Service Challenge J. Almeida, M. Dobson, A. Kazarov, G. Lehmann-Miotto, J.E. Sloper, I. Soloviev and.
M. Oldenburg GridPP Metadata Workshop — July 4–7 2006, Oxford University 1 Markus Oldenburg GridPP Metadata Workshop July 4–7 2006, Oxford University ALICE.
FTS monitoring work WLCG service reliability workshop November 2007 Alexander Uzhinskiy Andrey Nechaevskiy.
Pavel Nevski DDM Workshop BNL, September 27, 2006 JOB DEFINITION as a part of Production.
Summary of User Requirements for Calibration and Alignment Database Magali Gruwé CERN PH/AIP ALICE Offline Week Alignment and Calibration Workshop February.
The MEG Offline Project General Architecture Offline Organization Responsibilities Milestones PSI 2/7/2004Corrado Gatto INFN.
Summary of Workshop on Calibration and Alignment Database Magali Gruwé CERN PH/AIP ALICE Computing Day February 28 th 2005.
The DCS Databases Peter Chochula. 31/05/2005Peter Chochula 2 Outline PVSS basics (boring topic but useful if one wants to understand the DCS data flow)
1 A Scalable Distributed Data Management System for ATLAS David Cameron CERN CHEP 2006 Mumbai, India.
Report on database work for INB in ALICE Latchezar Betev (ALICE) Information Session INB – June 8, 2006.
Database Issues Peter Chochula 7 th DCS Workshop, June 16, 2003.
AliRoot Classes for access to Calibration and Alignment objects Magali Gruwé CERN PH/AIP ALICE Offline Meeting February 17 th 2005 To be presented to detector.
M.Frank, CERN/LHCb Persistency Workshop, Dec, 2004 Distributed Databases in LHCb  Main databases in LHCb Online / Offline and their clients  The cross.
Maria del Carmen Barandela Pazos CERN CHEP 2-7 Sep 2007 Victoria LHCb Online Interface to the Conditions Database.
ATLAS The ConditionDB is accessed by the offline reconstruction framework (ATHENA). COOLCOnditions Objects for LHC The interface is provided by COOL (COnditions.
M. Caprini IFIN-HH Bucharest DAQ Control and Monitoring - A Software Component Model.
ALICE Physics Data Challenge ’05 and LCG Service Challenge 3 Latchezar Betev / ALICE Geneva, 6 April 2005 LCG Storage Management Workshop.
AliRoot survey: Calibration P.Hristov 11/06/2013.
1 Tomasz Malkiewicz University of Jyväskylä Finland ALICE T0 detector Alignment and Calibration status ALICE Offline week.
L1Calo Databases ● Overview ● Trigger Configuration DB ● L1Calo OKS Database ● L1Calo COOL Database ● ACE Murrough Landon 16 June 2008.
CT-PPS DB Info (Preliminary) DB design will be the same as currently used for CMS Pixels, HCAL, GEM, HGCAL databases DB is Oracle based A DB for a sub-detector.
Database Replication and Monitoring
CMS High Level Trigger Configuration Management
ALICE analysis preservation
INFN-GRID Workshop Bari, October, 26, 2004
Calibrating ALICE.
Offline shifter training tutorial
Commissioning of the ALICE HLT, TPC and PHOS systems
ProtoDUNE SP DAQ assumptions, interfaces & constraints
Offline shifter training tutorial
TriggerDB copy in TriggerTool
ATLAS DC2 & Continuous production
Offline framework for conditions data
Presentation transcript:

1 Databases in ALICE L.Betev LCG Database Deployment and Persistency Workshop Geneva, October 17, 2005

17 October 2005Databases in ALICE 2 Outline  Transversal field and function of ALICE databases  Examples of database applications  Conditions DB and data collection models  Medium term plans  Conclusions

17 October 2005Databases in ALICE 3 Transversal field of the ALICE DBs  Detector Control System (DCS):  Application scope: configuration of systems and devices (modules and channels), front-end configuration (busses, thresholds); Archiving of monitored detectors and devices parameters  Size: millions of records, Tera bytes  High Level Trigger (HLT):  Application scope: mini-DST like TAG/ESD database for physics studies and offline event selection  Size: up to 10 9 events and 30TB per year  Detector Construction DB (DCDB):  Application scope: use by individual sub-detector groups and integration, repository and flow management for modules, components and their test data, cables, racks  Size: millions of records, Tera bytes  Experimental Control System (ECS):  Application scope: inclusion/exclusion of sub-detectors to a partition  Size: small number of small records

17 October 2005Databases in ALICE 4 Transversal field of the ALICE DBs  Data Acquisition (DAQ):  Application scope: parameter repository and resources assignment to DAQ tasks: configurations (current and stored), run parameters (current and stored)  Size: possibly large number of small records  Trigger:  Application scope: repository for trigger classes (input to Central Trigger Processor), definition of trigger masks  Size: large number of small records  Offline Conditions DB (CDB) – coupled to the Grid:  Application scope: non-event data for offline data reconstruction and analysis  Size: millions of files, Tera bytes  Distributed file catalogue, metadata and TAG DBs:  Application scope: raw data, production files, software catalogue and event tags  Size: hundreds of millions of records, Giga bytes

17 October 2005Databases in ALICE 5 Database applications - DCDB  Contains detector properties gathered during constructions time  Each detector group has one instance of DCDB with (detector) specific dictionary (PostgreSQL)  Read only copy at CERN (Oracle)  Content  Description of detector components  Measurements of response  Location of detector components  Geometry  Usage & lifetime  Input for calibration and geometry database  Lifetime of ALICE

17 October 2005Databases in ALICE 6 Database applications – DAQ and ECS logbook  Contains messages stored by DATE infoLogger, statistics extracted from logbook stream for each run statsCollector Daemon Process API Central server statsCollector (script) Console messages table logbook table Any DATE host logBook stream statsBrowser infoLogger MySQL DB operatorcron Launcher processes

17 October 2005Databases in ALICE 7 Databases relations and connectivity  Examples from previous slides:  DCDB – “quasi” distributed system, central repository is read- only, updates are infrequent  DAQ – completely closed central system  The biggest challenges remain the Grid file catalogue and offline conditions databases:  Used in a heterogeneous and often ‘hostile’ computing environment (the Grid).  Contains data from wide variety of sources

17 October 2005Databases in ALICE 8 Offline conditions DB relations DAQ Trigger DCS ECS Physics data DCDB AliEn/GLite: metadata file store calibration procedures calibration files AliRoot Calibration classes API files API HLT

17 October 2005Databases in ALICE 9 Considerations for Conditions DB  Sources for conditions DB and relations to other DBs are already quite complicated:  All databases potentially containing conditions information are “closed”, i.e. only accessible at CERN  It would be difficult to provide access methods to all DBs from the production and analysis code  ALICE uses ROOT as offline framework base:  Naturally defines the technology choice for object store – all conditions data are stored as root files  Additional condition - these files are read-only

17 October 2005Databases in ALICE 10 Considerations for Conditions DB (2)  Conditions data should be accessible in a Grid distributed production and analysis environment  The root files are registered in the Grid Distributed File Catalogue:  No need for distributed DBMS in a traditional sense and with all accompanying problems (access, replication, authentication) – a very big plus  Assures worldwide access to all files and associated tags  Drawbacks:  Replication of information  Depends almost entirely on the Grid file catalogue functionality

17 October 2005Databases in ALICE 11 Conditions DB – content and access  Update frequency:  The condition DB will have rather infrequent updates (max: once per run)  The objects themselves can have rich internal structure with finer granularity, depending on the detector calibration / alignment needs  Access framework:  Simple user interface and data identification (strings)  Automatically get the right valid object  Modification of the objects is handled through versioning  Same interface for different types of data sources (local file, Grid)

17 October 2005Databases in ALICE 12 Conditions DB – content and access (2)  Data organisation - simple filesystem-like storage:  Calibration/DETECTOR/FirstRun-LastRun.version

17 October 2005Databases in ALICE 13 Conditions DB – information gathering  Automated system – Shuttle:  Collecting conditions data from external DB at predetermined time intervals (for example at the end of every run)  Processing collected data using detector-specific preprocessor  Storing conditions data in the Conditions DB

17 October 2005Databases in ALICE 14 Conditions DB – information gathering (2)  Similar systems can be used to process conditions data from other sources:  Only new interfaces needed  The processing of the data is done in AliRoot (no change of framework)  Allows detector groups to do analysis and reduction of the raw data volume before storing it in the Conditions DB

17 October 2005Databases in ALICE 15 Medium term plans  Grid file catalogue is used routinely in ALICE since several years in the scope of the physics data challenges (PDC04, PDC05, SC3)  ROOT Grid access classes are now mature  AliRoot Conditions DB access framework is complete  Beginning of 2006 – Test of ALICE TPC with operational DCS and DAQ:  Test of both DBs and in addition the offline Conditions DB  Beginning of 2006 – Physics Data Challenge ’06:  Final test of the entire ALICE offline framework on the Grid, including test of Conditions framework

17 October 2005Databases in ALICE 16 Conclusions  ALICE has a rich field of databases used in the various groups for wide variety of tasks  The development of the majority of DBs is well advanced:  Some of them are already in production since several years  The biggest challenge remaining is to gather the information from all sources and make it available for Grid data reconstruction and analysis:  In this context, ALICE has decided to re-use the already existing Grid file catalogue technology  And enrich the AliRoot framework with tools allowing connectivity to all other DBs currently in existence