Difference between revisions of "Data Monitoring Database"

From GlueXWiki
Jump to: navigation, search
(Reconstruction Data Tables)
Line 6: Line 6:
  
 
=== Metadata 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.  
+
* 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
 
* Versions - version id (internal), release, CCDB version, timestamp, data type
  
Line 27: Line 27:
 
* # BCAL showers, FCAL showers, TOF points, SC hits, TAGM hits, TAGH hits
 
* # BCAL showers, FCAL showers, TOF points, SC hits, TAGM hits, TAGH hits
 
* # track matches to: BCAL, FCAL, TOF, SC
 
* # track matches to: BCAL, FCAL, TOF, SC
 
* Beam Energy
 
  
 
== Parameters ==
 
== Parameters ==
Line 34: Line 32:
 
* Data types - types of monitoring data that we are saving (online, offline, MC) [better terms?]
 
* Data types - types of monitoring data that we are saving (online, offline, MC) [better terms?]
 
* Data version
 
* Data version
 +
 +
== Histograms ==
 +
 +
=== Reconstruction Data ===
 +
* Beam Energy
 +
* Event Vertex Z
 +
* Track dE/dx: 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 θ,

Revision as of 07:48, 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, 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

Reconstruction Data

  • Beam Energy
  • Event Vertex Z
  • Track dE/dx: 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 θ,