Home

Welcome to the HGCAL DAQ wiki for 2017 Test Beams!

Here we should describe:

• Code of euDAQ
• Code for RPI
• Test page

Tasks

Description: Implementing "producer": We need to modify the producer to read in the status of the GPIO pins on target RPIs.

What to do: This will involve making an efficient connection with the PIs (i.e. more efficient than an ssh connection: possibly opening a UDP port and somehow accessing the status of the pins). We can probably reuse much of the python code that is meant to be run on the target RPIs, and suitably modify or rewrite it to run within EUDAQ. This will also involve modifying the Event class so that each EventPlane holds information regarding the RPI index and the status of the GPIO pins.

Assigned to:

Status: Incomplete

Description: Implementing "data collector": We need to modify the data collector to take as input some Event information and store it on disk in some convenient format.

What to do: This will involve modifying the DataCollector class so that is able to parse data coming in from the RPIs, appropriately concatenate it (or do whatever is required for EUDAQ to be able to store all the RAW data in some format). With lower priority at the moment, we also need to make a decoder, to translate this raw data into, for instance, an occupancy map, and to store this data in ROOT format.

Assigned to:

Status: Incomplete

Description: Implementing "data spoofer": We need to be able to test our whole DAQ chain independently of the hardware. This might be invaluable for debugging later.

What to do: This will involve either making the RPI spoof some data or the producer. The latter is easier to implement but the former will be more useful for debugging. For the moment, let's implement it at the producer level, with the RPI implementation being a lower priority.

Assigned to:

Status: Incomplete