Difference between revisions of "Data Monitoring Database"

From GlueXWiki
Jump to: navigation, search
Line 9: Line 9:
 
** Versions - version id (internal), release, CCDB version, timestamp, data type
 
** Versions - version id (internal), release, CCDB version, timestamp, data type
  
* Monitoring 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
 
** TAGH - pedestals, hit counts (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
 
** TAGH - pedestals, hit counts (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
Line 20: Line 20:
 
** FCAL - 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)
 
** PS  - pedestals, hit rate (mean, sigma), hit times (mean, sigma), minimum ionizing peak energies (mean, sigma)
** ANALYSIS - tracks (mean, sigma); neutrals (mean, sigma), avg. resolutions
 
  
 +
* Reconstruction Data Tables
 +
** Tracking: # tracks (by PID), avg. resolutions
 +
** Showers: # showers, avg. resolutions
 +
** Beam Photons: # photons
 +
** SC/TOF: # hits
  
 
'''Parameters'''
 
'''Parameters'''

Revision as of 00:04, 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

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
  • Raw Data Tables
    • Common info - run id, version id, # of events recorded in detector
    • 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: # tracks (by PID), avg. resolutions
    • Showers: # showers, avg. resolutions
    • Beam Photons: # photons
    • SC/TOF: # hits

Parameters

  • Data types - types of monitoring data that we are saving (online, offline, MC) [better terms?]
  • Data version