Difference between revisions of "Data Monitoring Database"
From GlueXWiki
(→Histograms) |
(→Histograms) |
||
Line 37: | Line 37: | ||
=== Calibration Data === | === Calibration Data === | ||
* Drift chamber residuals (mean & sigma) | * Drift chamber residuals (mean & sigma) | ||
− | * Timing resolutions | + | * Timing resolutions (SC, TOF, BCAL, FCAL, TAGM, TAGH) |
=== Reconstruction Data === | === Reconstruction Data === | ||
− | |||
* Event Vertex: Z, Y vs X | * Event Vertex: Z, Y vs X | ||
+ | * TAGM/TAGH: Photon Beam Energy | ||
* FCAL Showers: Energy, Time, Y vs X | * FCAL Showers: Energy, Time, Y vs X | ||
* BCAL Showers: Energy, Time, φ vs Z | * BCAL Showers: Energy, Time, φ vs Z | ||
Line 53: | Line 53: | ||
* For Good q+, q- (Track/Hit match, tracking FOM): Beta vs p | * For Good q+, q- (Track/Hit match, tracking FOM): Beta vs p | ||
* For Good p, pi+, pi-, K+, g (Track/Hit match, tracking FOM, PID FOM): Particle p vs θ, φ vs θ, Δβ vs p | * For Good p, pi+, pi-, K+, g (Track/Hit match, tracking FOM, PID FOM): Particle p vs θ, φ vs θ, Δβ vs p | ||
+ | * PID: Confidence Level, TOF & SC dE/dx vs p |
Revision as of 08:30, 24 September 2014
Draft Requirements for data quality monitoring database
The main purpose of this database is to display time series summaries of variables useful for data quality monitoring
Contents
Tables
Metadata tables
- Runs - run id (internal), run number, run start time/date, run stop time/date, # of events, nominal beam current, nominal beam energy, target type, target location (?), trigger configuration (e.g. a file name), solenoid field current, radiator, photon beam coherent peak.
- Versions - version id (internal), release, CCDB version, timestamp, data type
Raw Data Tables
- Common info - run id, version id, # of events recorded in detector
- Detector Systems: Group by detector region
- TAGH - pedestals, hit counts (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- TAGM - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- SC - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- CDC - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- FDC - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- TOF - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- BCAL - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- FCAL - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
- PS - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
Reconstruction Data Tables
- Tracking: # good/all tracks (q+, q-, p, pi-, pi+, K+)
- Neutral Showers: # good/all neutral showers
- # BCAL showers, FCAL showers, TOF points, SC hits, TAGM hits, TAGH hits
- # track matches to: BCAL, FCAL, TOF, SC
Parameters
- Data types - types of monitoring data that we are saving (online, offline, MC) [better terms?]
- Data version
Histograms
Calibration Data
- Drift chamber residuals (mean & sigma)
- Timing resolutions (SC, TOF, BCAL, FCAL, TAGM, TAGH)
Reconstruction Data
- Event Vertex: Z, Y vs X
- TAGM/TAGH: Photon Beam Energy
- FCAL Showers: Energy, Time, Y vs X
- BCAL Showers: Energy, Time, φ vs Z
- TOF Points: Energy, Time, Y vs X
- SC Hits: Sector, Time vs. Sector, Energy vs. Sector
- For p, pi+, pi-, K+, K-: Tracking chisq/ndf
- Track dE/dx vs p: CDC, FDC, TOF, SC
- Track Deposited Energy: BCAL, FCAL
- For Good q+, q- (Track/Hit match, tracking FOM): Beta vs p
- For Good p, pi+, pi-, K+, g (Track/Hit match, tracking FOM, PID FOM): Particle p vs θ, φ vs θ, Δβ vs p
- PID: Confidence Level, TOF & SC dE/dx vs p