Difference between revisions of "September 19, 2014 Data Monitoring"

From GlueXWiki
Jump to: navigation, search
(Action Items)
(Action Items)
Line 14: Line 14:
 
=== Action Items ===
 
=== Action Items ===
  
 +
* Mike will point us to collected EVIO data for the different detector systems as it becomes available.
 
* David is updating RootSpy and the documentation.
 
* David is updating RootSpy and the documentation.
 
** When he's finished, he'll contact the different detector groups and remind them to write their online monitoring plugins.  
 
** When he's finished, he'll contact the different detector groups and remind them to write their online monitoring plugins.  

Revision as of 15:45, 19 September 2014

Online Data Monitoring

What we want to know

  • Are the detectors working?
    • Do all of the channels have hits?
    • What are the hit counts/rates per channel?
    • Are the energies & times OK, garbage, or out of range? (by channel)
    • Is the reconstruction working?: Run full reconstruction over a small % of data, view tracking/shower-reconstruction results online (hdview2, monitoring_hists plugins).

Example

Action Items

  • Mike will point us to collected EVIO data for the different detector systems as it becomes available.
  • David is updating RootSpy and the documentation.
    • When he's finished, he'll contact the different detector groups and remind them to write their online monitoring plugins.
  • We (Paul?, David?, Sean?) will stay in contact with the detector groups, and make sure that they:
    • Write the plugins
    • Are histogramming the data we want (see above).
    • Integrate them into RootSpy, and determine which are the primary plots, the ones that are the most important for shift-takers.
  • Paul will make sure that the monitoring_hists plugin plots (for reconstruction quality) are integrated and viewable in RootSpy.

Offline Data Monitoring

What we want to know

  • Can we reproduce the online histograms offline:
    • Can we read data from tape?
    • Are all the channels present?
    • Are all the recorded values within the expected ranges?
  • How do the online histograms change as a function of time (e.g. hits/event vs run number)?
  • Calibration status/quality histograms (individual runs & a function of time)
  • Reconstruction status/quality histograms
    • Num tracks, showers, hits, etc.
    • Reconstructed track kinematics
    • Track / detector-hit matching
    • PID Quality
  • Analysis histograms
    • Can we see pi0 peaks
    • Can we see simple final states
      • γ p → p π+ π-
      • γ p → p π+ π- π0
      • γ p → p π+ π- η

Action Items

  • Paul, Sean: Make sure that the detector groups make plugins for doing the calibrations and viewing the quality/results.
  • Kei: Make cron-job scripts that automatically read EVIO data from tape, run the online/monitoring plugins, and make ROOT files with the desired histograms.
  • Sean: Make cron-job scripts that read the data from the ROOT files and: Store appropriate constants in a mysql database (e.g. hit rates, # reconstructed tracks/showers, calibration resolutions), and make png(?) files of important histograms on disk (hit occupancies, calibration plots, reconstructed track p vs. θ).
  • Kei (w/ Sean's help for database): Make
  • Make cron-job scripts for visualizing the data:
    • Make it easy to view today's & yesterday's online data (webpage?)
    • Make it easy to view data from any given run (webpage?)
    • Make it easy to view the status of things as a function of time (webpage?)

Links