IceCube Offline Database Overview Georges Kohnen Universit de Mons-Hainaut 07.09.2006 Zeuthen...
-
Upload
shannon-sims -
Category
Documents
-
view
220 -
download
0
description
Transcript of IceCube Offline Database Overview Georges Kohnen Universit de Mons-Hainaut 07.09.2006 Zeuthen...
IceCube Offline Database Overview
Georges KohnenUniversité de Mons-Hainaut
07.09.2006Zeuthen Collaboration Meeting
Today’s ride…
• Introduction• Database contents• Filling/Updating the Database, now and in
the future• Reading from the Database, interaction with
offline-software• Practical information• New features this year• To do
2
Introduction
• MySQL Database, “I3OmDb”• Contains / will contain most of 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 detectorDrilling: only string 21
Better calibrations: only string 21
Drilling: lots of strings
01/2004 01/2005 01/2006
“Qualifier”
Drilling01/2006Corr02/2005Drilling01/2005Initial
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 after domcal runs every few weeks/months
Very large sets of data (~100 MB per run for 9 strings)!
DOM Configuration (Detector Status) tables
9
• Updated once per run• Indexed by ConfigId
DOM Monitoring table
A
Under work, need to include post-monitoring results
Trigger tables
B
• Different design: triggers do not all have the same parameters
NEW!
“Lookup” tables
C
• 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
D
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)
Internal tables
E
• Set of tables that keep track of
• Updates / Revisions
• Start and End dates of records
• Comments
Filling the Database
• Until recently: filled from (text/.xml) data files, database created from scratch each time
• Since this year: automatic update of Run details, Trigger data and Detector Configuration/Status from DAQ on Pole DB for online use
• Then, regular synchronization of SouthPole I3OmDb with a reference Database in the northern hemisphere, and overall synchronization with this reference DB
• Manual updates/filling of non-regular data: Geometry, Domcal, ...
F
Using the I3OmDb Database at SouthPole
10
DAQ
PnF / Offline Softwareon SouthPole
SouthPoleI3OmDb
Fill run,trigger and
detector statusinformation
automatically
Sourcemodules
Othermodules
…
ReferenceI3OmDb
I3Dbservices
In testing now: 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”
I3Db Parameters
Practical Information
• Primary redundant Database server: icedb.umh.ac.be (also containing information about the content of the Database and about the I3Db services, as well as a public web-interface DEMONSTRATION)
• Mirrors: ppemons.umh.ac.be, dbs2.icecube.wisc.edu (should be used from the USA)
• Database Name: "I3OmDb"• Read-only login: username "www“
(> mysql -h "server" -u www)• Recommended tools for “brute” access:
– MySql Query Browser– MySql Control Center
12
New features this year
13
• On the database side:– Trigger storage tables– Continuous update of detector and trigger on SouthPole
(each run)• On the software side:
– I3Db turned into a set of services– Reconnection to DB in case of problem
To be done
14
• On the database side:– Store monitoring information from “human” detector
monitoring– Store precise status information about the DOMs– Store TWR data– Store Flasher data– 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
15
• Questions?
• ...?