Online Data Processing

Triggering

• Level-1 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:

• More details can be found at: Online Monitoring.

Calibrations

Calibration plugins and scripts are run on the data in the counting house as needed.

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:

Main drop-down menu:
- Blank (Invalid / Unknown) (-1)
- Production (0)
- Tests & Studies (sub-menu)
- Calibration (sub-menu)

"Tests & Studies" drop-down menu:
- DAQ Test (1)
- Trigger Test (2)
- Detector Test (3)
- Beam Studies (4)
- Noise Studies (5)
- Other Study/Test (100)

"Calibration" drop-down menu:
- Cosmic Run (101)
- Pulser Run (102)
- Pedestal Run (103)
- Alignment Run (104)
- LED Run (105)
- Normalization Run (106)
- Other Calibration (200)

• 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