Offline Data Processing
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
- The run-control database (RCDB) stores information about each run. The RCDB is located at:
WHERE AM I?
- During run start, information about the run setup are recorded in the RCDB. This includes run type, start time, trigger type, etc. This is performed by the script:
https://halldsvn.jlab.org/repos/trunk/online/daq/scripts/run_go
- Since the DAQ crashes sometimes, it cannot be relied on to report run summary information (e.g. run end-time, total # events, scalars, etc.). Instead, cron jobs on the online system periodically runs a script that crawls through the files and sets this information. The cron job scripts:
https://halldsvn.jlab.org/repos/trunk/online/etc/crontabs/crontab.hdsys.gluonraid1 https://halldsvn.jlab.org/repos/trunk/online/etc/crontabs/crontab.hdsys.gluonraid2
Launch the RCDB update script at:
https://halldsvn.jlab.org/repos/trunk/online/packages/monitoring/src/scripts/update_runinfodb.sh
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
