Difference between revisions of "Data Acquisition Shift"
| Line 21: | Line 21: | ||
This will bring up the screen for DAQ configuration: | This will bring up the screen for DAQ configuration: | ||
[[Image:Rcm.png| thumb | 600px | Fig. 1. ]] | [[Image:Rcm.png| thumb | 600px | Fig. 1. ]] | ||
| + | |||
| + | # Select run type | ||
| + | # Select detectors configuration (stored in COOL db) | ||
| + | # Select trigger | ||
| + | # Check boxes: | ||
| + | ## use_XTERM: if selected, then all processes will be started in foreground | ||
| + | ## use_ROCs : checked | ||
| + | ## use_debugger : | ||
== Run Control operation == | == Run Control operation == | ||
Revision as of 12:29, 13 June 2014
Contents
The Data Acquisition System (DAQ)
GlueX DAQ system is based on CODA software toolkit.
DAQ consists of ~50 embedded hardware readout controllers known as ROCs running LINIX OS, communicating with many other (data transfer, control and monitoring) processes. Data is transported between processors using standard network protocols (TCP/IP).
Routine Operation
Starting and stopping the DAQ System
Steps to start DAQ processes in case of all HW is powered up:
1. Login as hdops user on any gluonXX computer and execute:
HDOPS gluon47:~> cd CDAQ/ HDOPS gluon47:~/CDAQ> source online_setup.cshrc HDOPS gluon47:~/CDAQ> rcm.sh
This will bring up the screen for DAQ configuration:
- Select run type
- Select detectors configuration (stored in COOL db)
- Select trigger
- Check boxes:
- use_XTERM: if selected, then all processes will be started in foreground
- use_ROCs : checked
- use_debugger :
Run Control operation
DAQ for standalone run of subdetector can be started in interactive mode, when all processes open x-terminal window. Running whole system in this mode is impractical, due to a large number of windows (50+), and in this case most of processes should be strted in backgroung, keeping only run control window.
