1. IceCube Offline Database Overview Georges Kohnen Université de Mons-Hainaut 15.08.2007 IceCube Software Bootcamp

2. Introduction MySQL Database, “I3OmDb” Contains most of the non-physics information needed by offline- software, on the SouthPole, on a cluster or on your laptop: –Detector Geometry –InIce/IceTopCalibration –Detector/DOM Status and Trigger –Run Information – Monitoring information –Ice Properties –AMANDA and TWR information –Different “lookup” tables –Internal (bookkeeping) tables that keep track of Updates and Revisions Start and End times of records Comments 2

3. To be done 14 Store monitoring information from “human” detector monitoring Store Verification information (Bad DOM lists,...) Store Flasher data? Implement “Garbage” or “Temporary” database?...

4. 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/200401/200501/2006 “Qualifier” Drilling01/2006 Corr02/2005 Drilling01/2005 Initial

5. Geometry tables 5 AMANDA Geometry Planned geometry (IceCube80 with 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) and Corrections Drilling/Installation Season 3...

6. Filling the Database Since this Pole Season: 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

7. Using the I3OmDb Database at SouthPole 10 DAQ PnF / Offline Software on SouthPole SouthPole I3OmDb Fill run, trigger and detector status information automatically Source modules Other modules … Reference I3OmDb I3Db services Automatic synchronization of Pole and reference DBs (c.f. RevisionId)

8. Using the Database in offline-software I3Db project in offline-software (~11000 lines of code): new design: not one monolithic piece of code anymore, but –one service for each stream (geometry, calibration, detector status,…) –Conversion services (OMKey2MBId, OMNumber2OMKey,...) –one database service, responsible for connecting to the Database, retrieving/caching the data,… 11 I3OmDb Muxer / Modules Other modules … I3Db services Physics input I3Db retrieves the information according to the date of the event Offline chain of modules “hot-pluggable”

9. 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) 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

10. Demonstrations 15 4 ways to get info from the database  Python script in IceTray  Stand-alone program (MySQL Query Browser)  Database browser (web interface)  Terminal access (see bootcamp website for small tutorial) Database website with documentation, web interface, status page and this.ppt presentation: http://icedb.umh.ac.be