Difference between revisions of "Offline Analysis Commissioning"
From Hall D Ops Wiki
(→Data History Monitoring) |
|||
| Line 36: | Line 36: | ||
=== Action Items === | === Action Items === | ||
* Paul: Will integrate the monitoring_hists plugin (reconstruction) plots into RootSpy. | * Paul: Will integrate the monitoring_hists plugin (reconstruction) plots into RootSpy. | ||
| + | ** Will run full reconstruction over a small % of online data. | ||
* Detector groups: | * Detector groups: | ||
| Line 50: | Line 51: | ||
** γ p → p π<sup>+</sup> π<sup>-</sup> η | ** γ p → p π<sup>+</sup> π<sup>-</sup> η | ||
| − | == Monitoring | + | <!-- |
| + | == Monitoring Plan == | ||
| − | + | # (Kei): Will setup an automatic nightly script that submits jobs to the farm, runs over the EVIO data on tape with all of the monitoring plugins (raw, calibration, reconstruction, analysis), and saves the ROOT files to disk. | |
| + | # (Kei): Will periodically run a script that submits jobs to the farm that run over the EVIO data and remake the track reconstruction and calibration quality plots. | ||
| − | * | + | * How do the online histograms change as a function of time (e.g. hits/event vs run number)? |
* Paul: Will contact David & Mark and find locations to host the websites, mysql database, and ROOT files. | * 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: 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. | * Paul, Sean: Make sure that the detector groups make plugins for doing the calibrations and viewing the quality/results. | ||
| − | |||
** Raw data (hit occupancies) need to only be read once per run, calibration/reconstruction data need to be rerun and updated periodically. | ** 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: | * Sean: Make cron-job scripts that read the data from the ROOT files and: | ||
| Line 67: | Line 69: | ||
** Important histograms for each detector (png's created by Sean) | ** 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. | ** (w/ Sean's help for database access): Values in the mysql database as a function of run number. | ||
| + | --> | ||
<!-- | <!-- | ||
Revision as of 21:50, 22 September 2014
Contents
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?
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.
- 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 pi0 peaks
- Can we see simple final states
- γ p → p π+ π-
- γ p → p π+ π- π0
- γ p → p π+ π- η
