Difference between revisions of "Data Monitoring Database"

From GlueXWiki
Jump to: navigation, search
(Database Parameters)
(Database Parameters)
 
Line 78: Line 78:
 
== Database Parameters ==
 
== Database Parameters ==
  
* Data types - types of monitoring data that we are saving (online, offline, MC) [better terms?]
 
 
* Data version
 
* Data version
 
** Data type - rawdata, recon, mc-*
 
** Data type - rawdata, recon, mc-*
** Release - gluex_soft-comm-1.20
+
** Release - name of software version used to process data- gluex_soft-comm-1.20
** Timestamp - 20141110
+
** Timestamp - date when data processing began, i.e. when jobs were submitted - 20141110
** dataVersionString = rawdata_gluex_soft-comm-1.20_20141110
+
** dataVersionString = rawdata_gluex_soft-comm-1.20_20141110_whateveryouwant

Latest revision as of 13:11, 9 October 2014

Draft Requirements for data quality monitoring database & plots.

Histograms

Raw Data

  • Per Channel (2D preferred): Counts, Pedestals, Energy, Times
    • For: TAGH, TAGM, SC, CDC, FDC, TOF, BCAL, FCAL, PS
    • Examples for CDC:
integrated pulse
occupancy
pedestals

Click on each image to see full size.

Calibration Data

  • Drift chamber residuals (mean & sigma)
  • Timing resolutions vs. detector region (SC, TOF, BCAL, FCAL, TAGM, TAGH)
  • Other calibration spectra

Reconstruction Data

  • Event Vertex: Z, Y vs X
  • Detectors:
    • TAGM/TAGH Hits: # per event, Photon Beam Energy
    • FCAL Showers: # per event, Energy, Δt, Y vs X
    • BCAL Showers: # per event, Energy, Δt, φ vs Z
    • TOF Points: # per event, Energy, Δt, Y vs X
    • SC Hits: # per event, Sector, Δt, Energy vs. Sector
  • Tracks:
    • # Good, all tracks (q+, q-, p, pi-, pi+, K+)
    • # Track matches to: BCAL, FCAL, TOF, SC
    • 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
  • Neutrals:
    • # Good, all neutral showers
    • Kinematics (Good γ): Particle p vs θ, φ vs θ

Database Tables

  • The main purpose of the database is to display time series summaries of variables useful for data quality monitoring

Metadata tables

  • Runs
    • Run id (internal), run number, run start time/date, run stop time/date
    • # of events
    • Nominal beam current, nominal beam energy, radiator, photon beam coherent peak
    • Target type, target location (?)
    • Trigger configuration (e.g. a file name)
    • Solenoid field current
  • Versions
    • Version id (internal), release, CCDB version, timestamp, data type

Raw Data Tables

  • Common info: run id, file #, version id, # of events recorded in detector
  • Hit counts
    • For: TAGH, TAGM, SC, CDC, FDC, TOF, BCAL, FCAL, PS
    • Group by detector region: CDC rings, FDC planes (handle on r?), BCAL modules, SC paddles, FCAL ~θ(?), TOF paddle group(?)

Calibration Data Tables

  • Common info: run id, file #, version id, # of events
  • Drift chamber residuals (mean & sigma)
  • Timing Resolutions (mean & sigma): SC, TOF, BCAL, FCAL, TAGM, TAGH

Reconstruction Data Tables

  • Common info: run id, file #, version id, # of events
  • 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

Database Parameters

  • Data version
    • Data type - rawdata, recon, mc-*
    • Release - name of software version used to process data- gluex_soft-comm-1.20
    • Timestamp - date when data processing began, i.e. when jobs were submitted - 20141110
    • dataVersionString = rawdata_gluex_soft-comm-1.20_20141110_whateveryouwant