1 / 20

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.

lin
Télécharger la présentation

IceCube Offline Database Overview

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 6.6.06

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

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

  4. Introduction • The stored information is time -based • Records are “stacked” on each other • Example: Geometry Demonstration “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 every few weeks 8

  9. DOM Configuration tables Updated once per run 9

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

  11. DOM Monitoring table from Ignacio’s Monitoring files B

  12. Trigger tables • Different design: triggers do not all have the same parameters • New! Being tested right now… C

  13. “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 D

  14. 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) E

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

  16. Using the I3OmDb Database at SouthPole Offline chain of modules SouthPole version Source modules Other modules DAQ … To be done: automatic synchronization of Pole and reference DBs (c.f. RevisionId) I3Db services fill calibration 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) Offline-software V2 soon available! 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 … 11

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

  19. To be done • 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? 13

  20. This is the end 14

More Related