Difference between revisions of "Offline Analysis Commissioning"

From Hall D Ops Wiki
Jump to: navigation, search
(Offline Monitoring Plan)
Line 42: Line 42:
 
* Periodically submit jobs to monitor calibration & reconstruction quality of data on tape.  
 
* Periodically submit jobs to monitor calibration & reconstruction quality of data on tape.  
 
** Just a file or two from each run.  
 
** Just a file or two from each run.  
** Periodically: Either some fixed-time interval (every 2 weeks?) or perhaps after big changes.  
+
** Submit either at some fixed-time interval (every 2 weeks?) or perhaps after big changes.  
 
** Save key data in database, make history & key plots viewable on webpage
 
** Save key data in database, make history & key plots viewable on webpage
* When ready to do full reconstruction, run calibration & reconstruction quality plugins on all files, save key data to database & make viewable on webpage.  
+
* When ready to do full reconstruction, run calibration & reconstruction quality plugins on all files, save key data to database & make viewable on webpage.
  
 
=== Action Items ===
 
=== Action Items ===

Revision as of 18:12, 23 September 2014

Introduction

This document describes the goals of the data monitoring that will be carried out during the fall 2014 commissioning run of Hall D.

Raw Data

  • These questions are for every detector system: TAGH, TAGM, CDC, FDC, SC, TOF, BCAL, FCAL, PS (Pair Spectrometer)

Commissioning Tests

  • 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)
  • Can we read data from tape?
  • Can we reproduce the online histograms with offline data?

Offline Monitoring Plan

  • Pull key data/histograms from online histograms, put data in database, make history & plots viewable on webpage
  • Periodically test that we can reproduce online histograms using on-tape EVIO data.

Action Items

  • David: Online data monitoring environment (RootSpy, hdview2, etc.)
    • David is updating RootSpy and its documentation/instructions.
    • When he's finished, he'll contact the different detector groups and remind them to write their online monitoring plugins.
    • Make sure online monitoring histograms are archived somewhere.
  • Detector groups:
    • Writing the monitoring plugins for their systems.
    • Determining which plots are the primary plots (most important for shift-takers) and which are diagnostic plots.
    • Integrating their histograms into RootSpy.

Reconstruction Quality Monitoring

Commissioning Tests

  • What is the calibration quality of each system?
  • Can we perform reconstruction for each system? (Tracks, showers, etc.)
  • Are there any regions of the detector where reconstruction is inefficient?
  • Are tracks being properly matched to hits in the other detectors?
  • What is the quality of the particle ID?

Offline Monitoring Plan

  • Periodically submit jobs to monitor calibration & reconstruction quality of data on tape.
    • Just a file or two from each run.
    • Submit either at some fixed-time interval (every 2 weeks?) or perhaps after big changes.
    • Save key data in database, make history & key plots viewable on webpage
  • When ready to do full reconstruction, run calibration & reconstruction quality plugins on all files, save key data to database & make viewable on webpage.

Action Items

  • Paul: Will integrate the monitoring_hists plugin (reconstruction) plots into RootSpy.
    • Will run full reconstruction over a small % of online data.
  • Detector groups:
    • Writing the calibration scripts/programs/plugins for their systems.
    • Determining which plots are the primary plots and which are diagnostic plots.

Analysis Quality Monitoring

Commissioning Tests

  • Can we see π0 peaks
  • Can we see simple final states
    • γ p → p π+ π-
    • γ p → p π+ π- π0
    • γ p → p π+ π- η

Offline Monitoring Plan

  • Periodically submit analysis jobs to study π0's and simple final states.
    • Make key plots viewable on webpage.