Difference between revisions of "Offline Data Processing"
From GlueXWiki
(→Run Classification) |
(→Run Classification) |
||
| Line 42: | Line 42: | ||
* 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: | * 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: | ||
| − | Production Run | + | Type -1: Unknown |
| − | DAQ Test | + | Type 0: Production Run |
| − | Cosmic Run | + | Type 1: DAQ Test |
| − | Pulser Run | + | Type 2: Cosmic Run |
| − | Zero-Field Run | + | Type 3: Pulser Run |
| − | Empty Target Run | + | Type 4: Zero-Field Run |
| − | Misc. Test | + | 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 | * 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 Bits: | + | * Status Bits by File (Multiple bits may be set at once): |
| − | Non-Production Data | + | Status -1: Unknown |
| − | Low detector rates | + | Status 0: Production Data, Everything OK |
| − | + | ||
| − | Flux | + | Bit 1: Non-Production Data |
| − | Polarization | + | Bit 2: Low detector rates |
| + | Bit 3: Detector Malfunction | ||
| + | Bit 4: Flux Unknown | ||
| + | Bit 5: Polarization Unknown | ||
Revision as of 14: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
- 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 Bits by File (Multiple bits may be set at once):
Status -1: Unknown Status 0: Production Data, Everything OK
Bit 1: Non-Production Data Bit 2: Low detector rates Bit 3: Detector Malfunction Bit 4: Flux Unknown Bit 5: Polarization Unknown
