Difference: RichTestBeam2014DAQ (2 vs. 3)

Revision 32014-12-10 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichTestBeam2014"

RICH 2014 Testbeam DAQ

Line: 6 to 6
  The front-end data are acquired by the DBs (digital boards) that are connected to the ECs (elementary cells). The DBs capture events in response to external triggers (pulser or beam), format the data into MEPs (multi-event packets) and transmit the MEPs to the DAQ PC using Gbit Ethernet. Configuration of the DAQ and the front end electronics is via the same Gbit Ethernet links. The DAQ PC is located in the beam area.
Changed:
<
<
Control of the acquisition is done using a Java GUI. The GUI is also responsible for maintaining all the run and configuration preferences. A helper program (feb-proxy, that is started automatically by the GUI) forwards configuration packets to the DBs over the network and receives the data packets from the front-end. The packets are decoded by feb-proxy and the data saved in MDF format, one file per DB.
>
>
Control of the acquisition is done using Java GUIs. The JRichEcConfigurator GUI manages sets of elementary cell configuration parameters. The JRichEcControl GUI takes care of run control functions. These GUIs have superseded the ones used in the beam tests. The main difference is that the management of the EC configuration parameters and the run control functions have been separated. The GUIs are described in more detail in their respective topics. A helper program (feb-proxy, that is started automatically by the GUI) forwards configuration packets to the DBs over the network and receives the data packets from the front-end. The packets are decoded by feb-proxy and the data saved in MDF format, one file per DB.
  To start the DAQ, first log on to the DAQ account on the DAQ PC. This is usually done using ssh -Y from a PC in the control room. Type the command start_daqgui at the prompt to start the GUI. Changes to the settings are saved by the GUI and the last saved settings are restored when the GUI is started. A second GUI is used to control and monitor the trigger sources. To start it, use the start_trigger command then click on the Connect button.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback