Download - IceCube Offline Database Overview
IceCube Offline Database Overview
Georges Kohnen
Université de Mons-Hainaut
6.6.06
Today’s ride…
• Introduction
• Database contents
• Filling the Database, now and in the future
• Reading from the Database, interaction with offline-software
• Practical information
2
Introduction
• MySQL Database, “I3OmDb”• Contains / will contain all the non -physics
information needed by offline -software, on the SouthPole, on a cluster or on your laptop:– Detector Geometry / Calibration / Status / Run /
Monitoring / Trigger… information
– Ice Properties
– AMANDA information
– Different “lookup” tables
3
Introduction
• The stored information is time -based• Records are “stacked” on each other• Example: Geometry
4
Time
Planned Geometry, whole detector
Drilling: only string 21
Better calibrations: only string 21
Drilling: lots of strings
01/2004 01/2005 01/2006
“Qualifier”
Drilling01/2006
Corr02/2005
Drilling01/2005
Initial
Demo
nstrat
ion
Geometry tables
5
• AMANDA Geometry (recently corrected…)
• Planned geometry (IceCube + IceTop)
• Drilling/Installation Season 1 (string 21 and stations 21, 29, 30 and 39)
• Corrections to these coordinates (from Kurt)
• Drilling/Installation Season 2 (strings 29, 30, 38, 39, 40, 49, 50, 59 and stations 38, 40, 47, 48, 49, 50, 57, 58, 59, 66, 67, 74)
(= most “real” geometry presently available)
IceTop tables
6
AMANDA tables
7
Contents of “old” AMANDA omdb used by Sieglinde
Charge (Calibration) tables
8
from domcal .xml files
Updated every few weeks
DOM Configuration tables
9
Updated once per run
DOM Configuration tables
• There are 64 variables in these table: for 5000 DOMs and 1 run = 1 day, there are 117 million entries for just one year → waaaaaay too much!
• → Split this table up according to the frequency at which the variables change (once a run, once a year,…)
• This is one of the cases where input / documentation / coordination is still needed!
A
DOM Monitoring table
B
from Ignacio’s Monitoring files
Trigger tables
C
• Different design: triggers do not all have the same parameters
• New! Being tested right now…
“Lookup” tables
D
• OMId ↔ (string,tube) for AMANDA• DOM Serial number ↔ DOM location (string,tube)• DOM Serial number ↔ DOM name/nickname• RunId ↔ Run start date/time
Independent tables
E
IceProperties: Effective Scattering length and Absorption length for different wavelengths (in 10 nm bins), for cos θ = 0.80 and 0.94, and for different depths: Z in 10 m bins (X and Y not (yet) available)
Filling the Database
• Until recently: filled from (text/.xml) files, database created from scratch each time
• Since this past Pole season: automatic update of Detector Calibration/Status from DAQ for online use
• Then, regular synchronization of SouthPole I3OmDb with a reference Database in the northern hemisphere, and overall synchronization with this reference DB
F
Using the I3OmDb Database at SouthPole
10
DAQ
Offline chain of modulesSouthPole version
SouthPoleI3OmDb
fillcalibration anddetector status
informationautomatically
Sourcemodules
Othermodules
…
ReferenceI3OmDb
I3Dbservices
To be done: automaticsynchronization ofPole and reference DBs(c.f. RevisionId)
Using the Database in offline-software
• I3Db project in offline-software: new design: not one monolithic piece of code anymore, but– one service for each stream (geometry, calibration, detector status,…)– one database service, responsible for connecting to the Database,
retrieving/caching the data,…• IceProperties are currently not used in offline-software, thus
I3Db does not retrieve this information (yet)
11
I3OmDb
Sourcemodules
Othermodules
…
I3Dbservices
Physics input
I3Db retrieves the information according to the date of the event
Offline chain of modules
“hot-pluggable”
Offline-software V2
soon available!
Practical Information
• Primary Database server: icedb.umh.ac.be (containing information about the content of the Database and about the I3Db services)
• Secondary Database Servers: ppemons.umh.ac.be, dbs2.icecube.wisc.edu
• Database Name: "I3OmDb"• Read-only login: username "www“
(> mysql -h "server" -u www)
• Recommended tools:– MySql Query Browser– MySql Control Center
12
To be done
13
• On the database side:– Need to store monitoring information from “human”
detector monitoring
– Need to store precise status information about the DOMs
– Finalize complete DB synchronization
– Implement “Garbage” or “Temporary” database?
• On the software side:– Need to rethink caching process in I3Db
– New database services?
This is the end
14