Difference between revisions of "Data Monitoring Database"
From GlueXWiki
(→Raw Data Tables) |
(→Raw Data Tables) |
||
Line 11: | Line 11: | ||
=== Raw Data Tables === | === Raw Data Tables === | ||
* Common info - run id, version id, # of events recorded in detector | * Common info - run id, version id, # of events recorded in detector | ||
− | * | + | * Group by detector region (e.g. CDC rings, FDC planes (handle on r?), BCAL modules, SC paddles, FCAL ~θ(?), TOF paddle group(?)) |
− | * | + | * Pedestals, hit counts, mean minimum ionizing peak (MIP) energy |
− | ** TAGM | + | ** For: TAGH, TAGM, SC, CDC, FDC, TOF, BCAL, FCAL, PS |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
=== Calibration Data Tables === | === Calibration Data Tables === |
Revision as of 08:51, 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
- Group by detector region (e.g. CDC rings, FDC planes (handle on r?), BCAL modules, SC paddles, FCAL ~θ(?), TOF paddle group(?))
- Pedestals, hit counts, mean minimum ionizing peak (MIP) energy
- For: TAGH, TAGM, SC, CDC, FDC, TOF, BCAL, FCAL, PS
Calibration Data Tables
- Drift chamber residuals (mean & sigma)
- Timing Resolutions (mean & sigma): SC, TOF, BCAL, FCAL, TAGM, TAGH
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
Raw Data
- Per Channel: Counts, Pedestals, Energy, Times
Calibration Data
- Drift chamber residuals (mean & sigma)
- Timing resolutions (SC, TOF, BCAL, FCAL, TAGM, TAGH)
Reconstruction Data
- Event Vertex: Z, Y vs X
- Detectors:
- 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
- Tracks:
- Tracking chisq/ndf (p, pi+, pi-)
- Kinematics (Good p, pi+, pi-): Particle p vs θ, φ vs θ
- Deposited Energy (Good p, pi+, pi-): BCAL, FCAL
- PID dE/dx vs p (q+, q-): CDC, FDC, TOF, SC
- PID (q+, q-): β vs p
- PID (p, pi+, pi-): Confidence Level
- Neutrals:
- β vs p
- Kinematics (γ): Particle p vs θ, φ vs θ
- PID (γ): Confidence Level