Difference between revisions of "Online Data Processing"
From GlueXWiki
(→Low-Level Monitoring) |
|||
Line 1: | Line 1: | ||
+ | == Data Acquisition == | ||
+ | |||
== Triggering == | == Triggering == | ||
Line 4: | Line 6: | ||
* [[Level-3_Trigger | Level-3 Trigger]] | * [[Level-3_Trigger | Level-3 Trigger]] | ||
− | == | + | == Monitoring == |
− | + | * Monitoring of the data is performed as it arrives. This is done by running the monitoring plugins for the different detector systems in parallel with the data acquisition. The results are viewable in the counting house with RootSpy, and the histogram ROOT files are saved to: | |
− | [[Online_Monitoring_plugins | Online Monitoring]] | + | |
+ | * More details can be found at: [[Online_Monitoring_plugins | Online Monitoring]]. | ||
== Calibrations == | == Calibrations == | ||
Line 14: | Line 17: | ||
Talk to David: Make sure calibrations are integrated into scripts that are automatically run | Talk to David: Make sure calibrations are integrated into scripts that are automatically run | ||
− | |||
− | |||
− | |||
− | |||
== Run Information == | == Run Information == |
Revision as of 17:31, 20 January 2015
Contents
Data Acquisition
Triggering
Monitoring
- Monitoring of the data is performed as it arrives. This is done by running the monitoring plugins for the different detector systems in parallel with the data acquisition. The results are viewable in the counting house with RootSpy, and the histogram ROOT files are saved to:
- More details can be found at: Online Monitoring.
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
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
- During run pre-start, shift takers must indicate what the run type is for the run that is about to start. This run type is stored in the RCDB so that it can be used to help analyze the data. Possible run types include:
Type -1: Unknown Type 0: Production Run Type 1: DAQ Test Type 2: Cosmic Run Type 3: Pulser Run Type 4: Zero-Field Run Type 5: Empty Target Run Type 6: Misc. Test
- Further classification is performed by analyzing the rates in the various detector systems. If the rates in any system are lower than some threshold, then
- Status Values/Bits by File (Multiple bits may be set at once):
Status -1: Unknown Status 0: Production Data, Everything OK Status > 0: Bit 1: Non-Production Data Bit 2: Detector Malfunction Bit 3: Low detector rates Bit 4: Flux Unknown Bit 5: Polarization Unknown