Offline Analysis Commissioning

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 Monitoring

• 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?

Online 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.

• 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?

Action Items

• Paul: Will integrate the monitoring_hists plugin (reconstruction) plots into RootSpy.

• 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 pi0 peaks
• Can we see simple final states
  • γ p → p π⁺ π^-
  • γ p → p π⁺ π^- π⁰
  • γ p → p π⁺ π^- η

Data History Monitoring

• How do the online histograms change as a function of time (e.g. hits/event vs run number)?

• Is the reconstruction working?
  • Run full reconstruction over a small % of data, view tracking/shower-reconstruction results online (hdview2, monitoring_hists plugins).

• Paul: Will contact David & Mark and find locations to host the websites, mysql database, and ROOT files.
• Paul: Will contact David and make sure there is an easy way to access the configuration used for a given run (which detectors were connected/on/off, trigger configuration, did the DAQ crash or did the data get written to disk).
• 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 save the ROOT files to disk.
  • Raw data (hit occupancies) need to only be read once per run, calibration/reconstruction data need to be rerun and updated periodically.
• Sean: Make cron-job scripts that read the data from the ROOT files and:
  • Store appropriate data in an sqlite database (e.g. hit rates, # events, # reconstructed tracks/showers, calibration resolutions) as a function of run number.
  • Make png(?) files of important histograms on disk (hit occupancies, calibration plots, reconstructed track p vs. θ, etc.)
• Kei/Justin: Make cron-job scripts that create a version-0, "just get something working" webpage for viewing:
  • Important histograms for each detector (png's created by Sean)
  • (w/ Sean's help for database access): Values in the mysql database as a function of run number.