1. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 1 gallas@cern.ch Growing a Luminosity Database for Atlas Elizabeth Gallas Oxford University gallas@cern.ch December 2006

2. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 2 gallas@cern.ch Outline The 'Streaming Test 2006' Luminosity Database Schema (Tables, Views...) Input Simulation Data For the Streaming Test Evolution of the Streaming Test, placeholders Simple Query -- Output Cross Sections Input Real (Online) Data ConditionsDB Luminosity Database Distribution (Tier 0, 1, 2...)

3. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 3 gallas@cern.ch A Luminosity Database for Atlas This DB is ONE component of the “Streaming Test 2006” Purpose: Study online physics data streaming models Streaming Test 2006 -- Complete ATLAS simulation chain Generate MC Detector Simulation Trigger Simulation Data Reconstruction Data Analysis Cross Section calculation by Run/LBN/Trigger using a Database This DB reflects many features we need in the ATLAS Luminosity Database

4. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 4 gallas@cern.ch Start with something simple SQLite for the 'Test' – lightweight database engine Many advantages: Public domain, SQL based, portable, single file up to 2TB, no administrative overhead, command line access, many APIs (C/C++, python, TCL...) May be used at Tier 2 sites for ConditionsDB data... Plan is Use this SQLite LumDB for the Test Analyze relational structure for Conditions DB storage With a view that it might be re-extracted to SQLite at Tier 2...

5. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 5 gallas@cern.ch Schema – 2 Relational Tables Run_LBNs TableRun_LBN_Triggers Table ● Run_Number ● LBN ● Start_Time ● End_Time ● Duration (in seconds) ● Delivered_Lum (in nb-1) ● Live_Fraction ● Quality ● Run_Number ● LBN ● Trigger_Name ● L1_Accepts ● L2_Accepts ● L3_Accepts ● L1_Prescale ● L2_Prescale ● L3_Prescale

6. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 6 gallas@cern.ch Schema – a View ● LBN ● Trigger_Name ● Run_Number ● TRIG_LUM = ● DELIVERED_LUM * LIVE_FRACTION / PRESCALE ● TRIG_CROSS_SECTION = ● L3_ACCEPTS * PRESCALE / DELIVERED_LUM / LIVE_FRACTION V_RLT – Calculated luminosity quantities by trigger.

7. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 7 gallas@cern.ch Loading RunLumDB for the Streaming Test Columns populated from Ayana's log files: in RUN_LBNS.RUN_NUMBER, LBN in RUN_LBN_TRIGGERS.TRIGGER_NAME, L3_ACCEPTS. Other database columns Start, End_times, prescales, luminosity... populated with 'fake' data based on logical assumptions about what we expect the data to look like, will evolve with the Test. Placeholders for Deadtime, Prescales, Level 1,2 Accepts, Data Quality, Duration

8. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 8 gallas@cern.ch Online monitoring and offline analysis need Run,LBN,Trigger, Trigger Group, BCID dependent: Luminosity from detector scalars (normalized) Live fraction (1 – d) from Level 1 LBN duration, start and end times from Run Control (RC) Prescales (at all trigger levels) from Trigger configuration Number of accepted events (at each trigger level) From “Event Loss Monitoring”

9. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 9 gallas@cern.ch

10. Elizabeth Gallas Oxford University FILE: RunLumDB / 11-Dec-06 / Page 10 gallas@cern.ch Conclusions