Michele Floris SUMMARY OF FIRST LHC LOGGING DB

Michele Floris SUMMARY OF FIRST LHC LOGGING DB MEETING

Outline • Joint LHC machine experiments meeting: Interfacing to the LHC logging database for postprocessing (offline analysis). • Goals of this meeting: – Establish a first inventory of use cases and potential users – Discussion on required functionality – How to continue this? • Talks: – Users (Machine + Experiments) – Logging and measurement service Logging Database Use Case

LHC Beam Instrumentation • Quite some development already • Want at least same feature/performance Logging Database Use Case

ALICE DIP DCS OCDB Post-processing/calibration should be done centrally v 1 PROCESSING Delay of publication? API raw Logging Database Michele Floris Data format? Versions? 15/03/2010 What triggers the migration? Logging Database Use Case 4

ATLAS Value based queries impossible Michele Floris 15/03/2010 • They also use DIP as primary data source Logging Database Use Case 5

CMS Michele Floris 15/03/2010 Logging Database Use Case 6

LHCb Current drawbacks - We archiving everything on our own, including all beam and machine parameters, that we receive via DIP advantage: we have the same access interface to ONE database disadvantage: we always have to make sure we have everything and we clearly double the effort the tool should be interfaced to ANY database, each parameter or condition in the right database - We don’t have direct access to nominal settings and nominal parameters, like collimators settings, golden orbit, etc - BLM thresholds we have but we archive the whole set ourselves… - We don’t have access to the corrected and calibrated data May also allow correlating the whole set of data with shifters’ names in experiment control room and CCC…. Federico Alessio Logging Database Use Case 7

Current Status > 300 extraction clients 0. 4 2 million extraction requests per day PL/SQL filtered data transfer 7 Days raw data ~ 200’ 000 Signals ~ 50 data loading processes ~ 5. 1 billion records per day ~ 130 GB per day 46 TB per year throughput MDB ~20 Years LDB f FGC MK MS PIC WIC QPS BCT BLM BPM Cryo CIET Coll BIC BETS Rad VAC SU Exp VAC f f f f Equipment – DAQ – FEC 15 -Mar-2010 fff ~ 800’ 000 signals filtered data ~ 300 data loading processes ~ 3. 8 billion records per day ~ 105 GB per day 38 TB per year stored f ELEC CV EAU TIM COMM CNGS f f f f Equipment – DAQ – PLC f fff f Equipment – DAQ – PLC Forum on Interfacing to the Logging Database for Data Analysis 8

Data Extraction – Java API CERN Accelerator Logging Service 10 g AS Spring HTTP Remoting JDBC TS Data MDB TIMBER JDBC TS Data LDB JDBC Metadata Spring HTTP Remoting Custom Java Applications (currently > 30) 15 -Mar-2010 metadata They will only provide a JAVA interface (already used by timber and some 30 applications) We will need to implement a wrapper Forum on Interfacing to the Logging Database for Data Analysis 9

Misc from discussion • DIP not guaranteed to be reliable (uptime < 100%) – Access to DB mandatory • 2 main use cases – Running conditions (few users, lots of data) Direct access to logging DB – Offline analysis (many users, less data) Backfill of OCDB? • Central post-processing: commonly requested – Versions! Format? Same Logging DB? • Concurrent R/W: will also provide mirror DB? Michele Floris 15/03/2010 Logging Database Use Case 10

Most relevant variables • • bunch/beam intensities� beam losses beam positions beam sizes (emittances) collimator positions some vacuum gauges but also sporadically-measured quantities such as: – crossing angles – beta functions. Michele Floris 15/03/2010 Logging Database Use Case 11