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

From GlueXWiki
Jump to: navigation, search
(Links)
(Offline Data Monitoring)
Line 29: Line 29:
 
* Calibration status/quality histograms (individual runs & a function of time)
 
* Calibration status/quality histograms (individual runs & a function of time)
 
* Reconstruction status/quality histograms
 
* Reconstruction status/quality histograms
**  
+
** Num tracks, showers, hits, etc.
 +
** Reconstructed track kinematics
 +
** Track / detector-hit matching
 +
** PID Quality
 
* Analysis histograms
 
* Analysis histograms
** Can we see pi0, etc. peaks,
+
** Can we see pi0, etc. peaks
 +
** Etc.
  
 
=== Action Items ===
 
=== Action Items ===
  
 +
* Make sure that the detector groups make plugins for doing the calibrations and viewing the quality/results.
 
* Make cron-job scripts that automatically read data from disk and make histograms of the above.  
 
* Make cron-job scripts that automatically read data from disk and make histograms of the above.  
 
* Make cron-job scripts for visualizing the data:
 
* Make cron-job scripts for visualizing the data:
Line 40: Line 45:
 
** Make it easy to view data from any given run (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?)
 
** Make it easy to view the status of things as a function of time (webpage?)
 
  
 
== Links ==
 
== Links ==
 
* CLAS g13 experiment [http://clasweb.jlab.org/rungroups/g13/monitor/monitorwrapper.html Offline Monitoring Plots]
 
* CLAS g13 experiment [http://clasweb.jlab.org/rungroups/g13/monitor/monitorwrapper.html Offline Monitoring Plots]
 
* CLAS g13 experiment [http://clasweb.jlab.org/rungroups/g13/anamon/g13awrapper.html Calibration Monitoring Plots]
 
* CLAS g13 experiment [http://clasweb.jlab.org/rungroups/g13/anamon/g13awrapper.html Calibration Monitoring Plots]

Revision as of 13:54, 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 rates per channel?
    • Are the energies & times OK or garbage (by channel)?

Example

Action Items

  • David is updating RootSpy and the documentation.
  • When he's finished, he'll contact the different detector groups and have them write their monitoring plugins.
  • We need to stay in contact with those groups, and make sure that they:
    • Write the plugins
    • Integrate them into RootSpy (visualization macros?)
    • Are histogramming the data we want (see above)

Offline Data Monitoring

What we want to know

  • Can we reproduce the online histograms offline:
    • Can we ready 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, etc. peaks
    • Etc.

Action Items

  • Make sure that the detector groups make plugins for doing the calibrations and viewing the quality/results.
  • Make cron-job scripts that automatically read data from disk and make histograms of the above.
  • 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