Data Monitoring Database
From GlueXWiki
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
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.
- Versions - version id (internal), release, CCDB version, timestamp, data type
- Monitoring data tables
- Common info - run id, version id, # of events recorded in detector
- TAGH - hit rate (mean, sigma), hit times (mean, sigma)
- TAGM - hit rate (mean, sigma), hit times (mean, sigma)
- SC - hit rate (mean, sigma), hit times (mean, sigma)
- CDC - hit rate (mean, sigma), hit times (mean, sigma)
- FDC - hit rate (mean, sigma), hit times (mean, sigma)
- TOF - hit rate (mean, sigma), hit times (mean, sigma)
- BCAL - hit rate (mean, sigma), hit times (mean, sigma)
- FCAL - hit rate (mean, sigma), hit times (mean, sigma)
- PS - hit rate (mean, sigma), hit times (mean, sigma)
- ANALYSIS - tracks (mean, sigma); neutrals (mean, sigma), avg. resolutions
Parameters
- Data types - types of monitoring data that we are saving (online, offline, MC) [better terms?]
- Data version