1 / 21

Comprehensive Overview of IceCube Offline Database Management and Features

This document presents a detailed overview of the IceCube Offline Database (I3OmDb) managed by Georges Kohnen from Université de Mons-Hainaut. It covers the structure, content, and functionality of the database as it relates to non-physics information crucial for offline software operations. The presentation includes practical insights into filling and updating processes, the integration of new features, and the interaction between the database and offline software. It also outlines the storage of various geometrical and calibration data, along with future enhancements and synchronization strategies between the IceCube collaboration teams.

tracy
Download Presentation

Comprehensive Overview of IceCube Offline Database Management and Features

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IceCube Offline Database Overview Georges Kohnen Université de Mons-Hainaut 07.09.2006 Zeuthen Collaboration Meeting

  2. 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

  3. 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

  4. Introduction • The stored information is time -based • Records are “stacked” on each other • Example: Geometry “Qualifier” Drilling01/2006 Corr02/2005 Drilling01/2005 Initial Drilling: lots of strings Better calibrations: only string 21 Drilling: only string 21 Planned Geometry, whole detector Time 01/2004 01/2005 01/2006 4

  5. Geometry tables • 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) 5

  6. IceTop tables 6

  7. AMANDA tables Contents of “old” AMANDA omdb used by Sieglinde 7

  8. Charge (Calibration) tables from domcal .xml files Updated after domcal runs every few weeks/months Very large sets of data (~100 MB per run for 9 strings)! 8

  9. DOM Configuration (Detector Status) tables • Updated once per run • Indexed by ConfigId 9

  10. DOM Monitoring table Under work, need to include post-monitoring results A

  11. Trigger tables • Different design: triggers do not all have the same parameters NEW! B

  12. “Lookup” tables • OMId ↔ (string,tube) for AMANDA • DOM Serial number ↔ DOM location (string,tube) • DOM Serial number ↔ DOM name/nickname • RunId ↔ Run start date/time C

  13. Independent tables 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) D

  14. Internal tables • Set of tables that keep track of • Updates / Revisions • Start and End dates of records • Comments E

  15. 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

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

  17. 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) I3Db retrieves the information according to the date of the event I3Db services I3OmDb “hot-pluggable” Physics input Source modules Other modules Offline chain of modules … I3Db Parameters 11

  18. 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

  19. New features this year • 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 13

  20. To be done • 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? 14

  21. This is the end • Questions? • ...? 15

More Related