RpiProducer

What is this

This page describes producer code that was used for data-taking in May 8-15 beam tests. It is based on the RpiTestProducer and if you're reading this for learning euDAQ, it's recommended to study that code first: see RpiTestProducer wiki page. Perhaps the only difference from that code is an implementation of the possibility to send a command with a run number (START_RUN runnum) via TCP communication.

The code is located under producers/cmshgcal and because the other producer in this directory requires IPBus, it will compile only on machines with IPbus (aka Cactus) installed. That means only SLC6/CC7, but not Ubuntu :(
See IPBus wiki on how to install cactus.

Instructions on how to run euDAQ during the data-taking is located on this twiki for beam tests.

Here, we will only describe how to run it with emulation of the data-taking. For that we will need real data files taken by RPI. These files can be found on svhgcal01 computer at /disk2_2TB/data/. Copy a few of them locally.

Tcp server script

During real data-taking the scripts/RpiDaqTcp.py script was used (note: it may not be up-to-date on this github, the latest version is on the raspberry).
For the emulation we will use another script, scripts/LocalDataOverTCP.py, which is very similar but has less options. It only transfers an existing file to euDAQ.

• Start the server with:

./LocalDataOverTCP.py -f RUN_0106_120517_0609.raw.txt

• If that script and euDAQ are to be run on different computers (which is possible), then MYIP variable should be changed in the header of the above script.

Rpi producer

It implements low-level socket connections to the TCP server, sends start/stop commands and receives the data. Here is how to start it:

• Keep the LocalDataOverTCP running in one of the terminals.
• From another terminal, go to the root of eudaq and execute: ./STARTRUN rpi. This will start the producer.
• Load config file from producers/cmshgcal/conf/RpiProducer.conf
• Now, you can Start and Stop runs. Observe the messages in LogCollector and other windows.
• Online Monitor should present some DQM plots, in shape of hexagons.
  • The online monitor is now moved to producers/cmshgcal/onlinemon sub-directory. This is where one should implement new plots etc.