Difference between revisions of "Online Data Processing"

From GlueXWiki
Jump to: navigation, search
(Created page with "== Triggering == * Level-1 Trigger * Level-3 Trigger == Low-Level Monitoring == This is performed by running the monitoring plugins...")
 
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
<!--
 
== Triggering ==
 
== Triggering ==
  
Line 4: Line 5:
 
* [[Level-3_Trigger | Level-3 Trigger]]
 
* [[Level-3_Trigger | Level-3 Trigger]]
  
== Low-Level Monitoring ==
+
== 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.
+
* 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:
https://halldweb1.jlab.org/wiki/index.php/Online_Monitoring_plugins
+
 
 +
* More details can be found at: [[Online_Monitoring_plugins | Online Monitoring]].  
  
 
== Calibrations ==
 
== 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.
+
Calibration plugins and scripts are run on the data in the counting house as needed.
 
+
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 ==
 
== Run Information ==
Line 37: Line 33:
  
 
  https://halldsvn.jlab.org/repos/trunk/online/packages/monitoring/src/scripts/update_runinfodb.sh
 
  https://halldsvn.jlab.org/repos/trunk/online/packages/monitoring/src/scripts/update_runinfodb.sh
 
+
-->
 
== Run Classification ==
 
== 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:
 
* 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
+
<pre>
Type 0: Production Run
+
Main drop-down menu:
Type 1: DAQ Test
+
- Blank (Invalid / Unknown) (-1)
Type 2: Cosmic Run
+
- Production (0)
Type 3: Pulser Run
+
- Tests & Studies (sub-menu)
Type 4: Zero-Field Run
+
- Calibration (sub-menu)
Type 5: Empty Target Run
+
Type 6: Misc. Test
+
  
 +
"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)
 +
</pre>
 +
<!--
 
* 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 by File (Multiple bits may be set at once):
+
* Status Values/Bits by File (Multiple bits may be set at once):
  
 
  Status -1: Unknown
 
  Status -1: Unknown
 
  Status 0: Production Data, Everything OK
 
  Status 0: Production Data, Everything OK
 
+
  Status > 0:
  Bit 1: Non-Production Data
+
  Bit 1: Non-Production Data
Bit 2: Low detector rates
+
  Bit 2: Detector Malfunction
Bit 3: Detector Malfunction
+
  Bit 3: Low detector rates
Bit 4: Flux Unknown
+
  Bit 4: Flux Unknown
Bit 5: Polarization Unknown
+
  Bit 5: Polarization Unknown
 +
-->

Latest revision as of 13:11, 11 February 2015

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)