Difference between revisions of "Offline Data Processing"
(→Run Information) |
|||
| Line 23: | Line 23: | ||
* During run start, information about the run setup are recorded in the online run-control database (RCDB). This includes run type, start time, trigger type, etc. This is performed by the script at: | * During run start, information about the run setup are recorded in the online run-control database (RCDB). This includes run type, start time, trigger type, etc. This is performed by the script at: | ||
| − | + | https://halldsvn.jlab.org/repos/trunk/online/daq/scripts/run_go | |
* Periodically, a | * Periodically, a | ||
Revision as of 12:40, 20 January 2015
Contents
Triggering
Low-Level Monitoring
This is performed by running the monitoring plugins for the different detector systems on data as it arrives. The results are viewable in the counting house with RootSpy. https://halldweb1.jlab.org/wiki/index.php/Online_Monitoring_plugins
Calibrations
Calibration plugins and scripts are automatically run on the data as it arrives. These scripts are responsible for fitting peaks, checking constants into the calibration database, and iterating as necessary.
Talk to David: Make sure calibrations are integrated into scripts that are automatically run
Reconstruction Monitoring
This is performed by running the monitoring_hists plugin on data after it is calibrated. The results are viewable in the counting house with RootSpy.
Run Information
- During run start, information about the run setup are recorded in the online run-control database (RCDB). This includes run type, start time, trigger type, etc. This is performed by the script at:
https://halldsvn.jlab.org/repos/trunk/online/daq/scripts/run_go
- Periodically, a
David: cron job into text file
add to pre-start script: enhance dmitry's system
Talk to David/Sean: Ask what their plans are.
Run Classification
Talk to David: Shift-takers recording if production data or not
talk to sergey: list of info needed at beginning and end of run
