Difference between revisions of "Data Acquisition Shift"

From Hall D Ops Wiki
Jump to: navigation, search
(Expert personnel)
(Starting and stopping the DAQ System)
Line 15: Line 15:
 
1. Login as <b>hdops</b>  user on any <b>gluonXX</b>  computer and execute:
 
1. Login as <b>hdops</b>  user on any <b>gluonXX</b>  computer and execute:
 
<pre>
 
<pre>
HDOPS gluon47:~> cd CDAQ/
 
HDOPS gluon47:~/CDAQ> source online_setup.cshrc
 
 
HDOPS gluon47:~/CDAQ> rcm.sh
 
HDOPS gluon47:~/CDAQ> rcm.sh
 
</pre>
 
</pre>

Revision as of 11:45, 21 October 2014

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:~/CDAQ> rcm.sh

This will bring up the screen for DAQ configuration (Fig. 1.):

Fig. 1. DAQ Control GUI
  1. Select run type
  2. Select detectors configuration (stored in COOL db)
  3. Select trigger
  4. Check boxes:
    1. use_XTERM: if selected, then all processes will be started in foreground
    2. use_ROCs : checked
    3. use_debugger :


For standalone run of single subdetector, the DAQ can be started in interactive mode, when all processes open x-terminal window (Fig. 3.). 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 started in backgroung, keeping only run control window.

Run Control operation

Fig. 2. Run Control GUI

Advanced Details of the DAQ System

Fig. 3. Example of desktop after DAQ is started


Expert personnel

The individuals responsible for checking that the DAQ is ready to take data and setting its operating parameters are shown in following table. Problems with normal operation of the DAQ should be referred to those individuals and any changes to their settings must be approved by them. Additional experts may be trained by the system owner and their name and date added to this table.

Table: Expert personnel for the DAQ system
Name Extension Date of qualification
Sergey Furletov 269-5332 May 20, 2014