1 / 4

Database Considerations

Database Considerations. SVD Meeting. Which Databases?. Construction Database Definition of parts and assemblies Testing results measured during construction Detector Configuration Database Information needed when starting a run Hardware related data Monitoring Database

tucker-bender
Download Presentation

Database Considerations

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. Database Considerations Markus Friedl (HEPHY Vienna) SVD Meeting

  2. Which Databases? • Construction Database • Definition of parts and assemblies • Testing results measured during construction • Detector Configuration Database • Information needed when starting a run • Hardware related data • Monitoring Database • Environmental condition (temperature, radiation, …) data • Frequently updated • Alignment Database • Needed for tracking • Software related data Markus Friedl (HEPHY Vienna)

  3. Detector Configuration Database • These data are needed when starting a run: • Basic Geometry Information • Assignment of chips/ladders/channels/readout modules/… • Hardware Configuration Data • Bias voltages, APV25 settings, FADC settings, … • Couple of values (mostly integer) for each {sensor, hybrid, FADC board, …} • Size: minimal Markus Friedl (HEPHY Vienna)

  4. Additional Data Not Stored in Database • Generated at start of each run: • Strip properties: Pedestal, Noise, Threshold, Flag • Total size: ~4MB • Generated with each calibration (local run, once/day): • Strip properties: Gain • FADC properties: Hit time finding lookup table • Total size: ~6MB • Why not in database? • Not of interest for later stages except strip gains • Compact information in a single file per run/calibration • Would quickly add huge amount of (unneeded) data to database Markus Friedl (HEPHY Vienna)

More Related