Download pdf - AIDA-2020 Deliverable - CERNcds.cern.ch/record/2294789/files/AIDA-2020-D5_5.5.pdfAIDA-2020 Consortium, 2017 Grant Agreement 654168 PUBLIC 1 / 9 Grant Agreement No: 654168 AIDA-2020

AIDA-2020-D5.5

AIDA-2020Advanced European Infrastructures for Detectors at Accelerators

Deliverable Report

Online data model available

Irles, A. (CNRS-LAL, DESY) et al

30 November 2017

The AIDA-2020 Advanced European Infrastructures for Detectors at Accelerators projecthas received funding from the European Union’s Horizon 2020 Research and Innovation

programme under Grant Agreement no. 654168.

This work is part of AIDA-2020 Work Package 5: Data acquisition system for beam tests.

The electronic version of this AIDA-2020 Publication is available via the AIDA-2020 web site<http://aida2020.web.cern.ch> or on the CERN Document Server at the following URL:

<http://cds.cern.ch/search?p=AIDA-2020-D5.5>

Copyright c© CERN for the benefit of the AIDA-2020 Consortium

http://aida2020.web.cern.ch

http://cds.cern.ch/search?p=AIDA-2020-D5.5

AIDA-2020 Consortium, 2017

Grant Agreement 654168 PUBLIC 1 / 9

Grant Agreement No: 654168

AIDA-2020 Advanced European Infrastructures for Detectors at Accelerators

Hor izon 2020 Research In f rast ructures pro ject AIDA -2020

DELIVERABLE REPORT

ONLINE DATA MODEL AVAILABLE

DELIVERABLE: D5.5

Document identifier: AIDA-2020-D5.5

Due date of milestone: End of Month 30 (October 2017)

Report release date: 30/11/2017

Work package: WP5: Data acquisition system for beam tests

Lead beneficiary: DESY

Document status: Final

Abstract:

This document summarizes the event model definition and a test thereof for common data acquisition

(DAQ) and data quality monitoring (DQM).


Deliverable: D5.5

Date: 30/11/2017


AIDA-2020 Consortium, 2017

For more information on AIDA-2020, its partners and contributors please see www.cern.ch/AIDA2020

The Advanced European Infrastructures for Detectors at Accelerators (AIDA-2020) project has received funding from the

European Union’s Horizon 2020 Research and Innovation programme under Grant Agreement no. 654168. AIDA-2020

began in May 2015 and will run for 4 years.

Delivery Slip

Name Partner Date

Authored by A. Irles

R. Ete

LAL/DESY

DESY 13/11/2017

Edited by L. Lapadatescu CERN 13/11/2017

Reviewed by M. Wing [WP5 coordinator]

F. Sefkow [Scientific coordinator]

UCL

DESY 24/11/2017

Approved by F. Sefkow [Scientific coordinator]

Steering Committee

30/11/2017

http://aida2020.web.cern.ch/


Deliverable: D5.5

Date: 30/11/2017


TABLE OF CONTENTS

1. Introduction ...................................................................................................................................... 4

2. Online EUDAQ event model ........................................................................................................... 4

3. Event model for online data quality monitoring .............................................................................. 5

4. Event model for common beam tests ............................................................................................... 6

5. Proof of concept ............................................................................................................................... 7

6. References ........................................................................................................................................ 8

Annex: Glossary ................................................................................................................................... 9


Deliverable: D5.5

Date: 30/11/2017


Executive summary

In this document, we report on the online model definition succesfully tested in a set of combined

beam tests of a beam telescope and the analogue hadronic calorimeter technological prototype for

the linear collider.

Sections 2 and 3 are dedicated to the event model implementation for the online event synchronization

using EUDAQ 2 software and for quality monitoring using the DQM4HEP online monitor framework.

In Section 4 we present an event model general case implementation of common test beam within

AIDA2020 WP5 standards.

Finally, in Section 5, we refer to the success of the event model for common beam tests in a real case

example: the combined beam test of the beam telescope and the analogue hadronic calorimeter at the

DESY beam line.

1. INTRODUCTION

This deliverable document is largely based in the AIDA2020-MS47 document [1] where we report

on the online model definition, development and test in a set of combined beam tests of a beam

telescope and the analogue hadronic calorimeter technological prototype for the linear collider. In the

milestone document, we discussed the work of WP5 task 5.5 in the pursuit of the definition of the

event model. The first part of the document was dedicated to a summary report of the status of

EUDAQ 2 [2] which is the data acquisition framework used and developed by WP5 and for combined

beam tests of linear collider detectors. We referred to online documentation and other WP5 milestones

reports. The second part, and the core of the document, was dedicated to the event model definition

inside EUDAQ 2, its most important features and its implementation for the online data quality

monitoring and the fostered synergies with the DQM4HEP online monitor framework. Finally, we

presented and discussed the proof of concept case: the combined beam test of the beam telescope and

the analogue hadronic calorimeter at the DESY beam line.

In this deliverable document, we will basically highlight the main ideas and facts described in the

AIDA2020-MS47.

2. ONLINE EUDAQ EVENT MODEL

The event model is based in the eudaq::Event class: the most important data container in the EUDAQ

system (we refer to the AIDA-2020-MS47 document and to the EUDAQ manual for more detailed

information). Data acquired by the devices are saved as an eudaq::Event in the Producer (detector

specific software modules for hardware control and data acquisition) with an associated m_type, see

Table 1, used afterwards in the DataCollector as identifier for data conversion if needed and a variable

that allows identification of the acquisition time to which it belongs, making possible the merging in

the DataCollector with other events collected by other Producers. These identifiers can be a trigger

ID provided by an external device, an internal or external timestamp, an internal event number counter

or any combination of them. It is at this level, DataCollector (generic EUDAQ 2 module where the

data from different Producers is merged) level, where the real events containing information of all (or

a few) of the devices in the beam test are built.


Deliverable: D5.5

Date: 30/11/2017


In addition, the eudaq:Event m_blocks variable allows the data to be stored in any kind of format.

Here is where the different Producers should keep the full event information (collected charge for all

channels, digital signals, etc.) and does not need to be, in principle, decoded in any way to be sent to

the DataCollector as long as this information is not needed for the basic event building.

Table 1: All member variables in eudaq::Event

eudaq::LCEvent

This is an EUDAQ wrapper for the LCIO [3] container. This is a derived class from eudaq::Event

which facilitates the online conversion to LCIO during the event merging at the DataCollector level.

Although this and eudaq::Event have been developed in the context of Linear Collider and telescope

experiments (which use LCIO objects for event definition), this object is general enough to be used

for all kind of detectors as long as they want to use LCIO format for their analysis/monitoring

offline/online tools.

3. EVENT MODEL FOR ONLINE DATA QUALITY MONITORING

During discussions with several groups about the online data quality monitoring approach for

common beam tests, WP5 has established a strong collaboration with DQM4HEP [4] developers. It

is designed for use as a generic online monitor for particle physics experiments, ranging from small

table-top experiments to large multi-detector test-beams set-ups, such as those currently

ongoing/planned at the DESY2 or CERN SPS beamlines. It has been used successfully by several

groups and detectors: i.e. telescopes and CALICE AHCAL and SDHCAL.

The software provides, among others features, a DAQ system entry point to feed the system with raw

data, a raw data distributed system using the server/client paradigm and a histogram distributed

system and visualization interfaces.

It is designed to accept any C++ serialized object as a raw event but AIDA-2020 WP5 advises to use

LCIO objects, since

- they are flexible and we also benefit from the technical support provided by the

AIDA-2020 WP3;


Deliverable: D5.5

Date: 30/11/2017


- they are extensively used by most of linear collider offline tools;

- EUDAQ 2 eudaq::LCEvent allows for an easy online conversion from eudaq::Event.

Eventually, EUDAQ and DQM4HEP can tailor there streaming facilities to a common one, resulting

in an improvement of speed and memory use at the interface between EUDAQ and DQM4HEP.

PODIO, being developed by AIDA-202 WP3, could be the most promising solution with Plain-Old

Data structures as the model, with support for vectorization and thus a fast IO streaming.

It is important to remark that the basic event building is done at the DataCollector level in EUDAQ

and that LCIO objects are event based objects. They can contain several collections with information

for the different (all or some) detectors that correspond to the same time slice data acquisition.

Therefore, DQM4HEP will easily account for correlations and allows deeper online event building to

be performed (i.e. search of tracks) without modifying the data.

4. EVENT MODEL FOR COMMON BEAM TESTS

The overview picture of the proposed model can be seen in Figure 1 and it is extensively explained

in the AIDA-2020 MS47 report. It relies on two different frameworks which are modular and scalable

and can be easily coupled to standalone DAQ developments without requiring large modifications.

The first step, for every group involved in a common beam test, consists on the adaptation of their

DAQ software to the EUDAQ 2 framework. This means the writing of Producer which will receive

the data from the hardware under test or from the standalone DAQ of this hardware. The second

option allows the different groups to continue using and developing their own DAQ software, since

in this second case, EUDAQ acts as simple run control and data collecting framework. At the

Producer level, the user should create standalone events with a trigger ID, event number or timestamp

that can be understood by the other devices. It is important to remark here that it is the responsibility

of the different detector groups to make sure that there is sufficient information for event building

provided by the Producer. For example, there might be the need to provide a “translation” between

time stamp and trigger number. The EUDET Trigger Logic Unit (TLU) [5] is a “standard” device for

this (see Section 5.1 for an example case). Another possible situation would be when one of the

devices under test is not able to identify the event within an integration time (or readout cycle) but

needs geometric information from another device to make the event building. In all cases, the groups

will have to provide at Producer level all the needed information for the common event building.

The second step consists of writing of a DataCollector for all devices under test. This is a common

task since it requires knowledge of how events are merged and requires from the groups that they

provide needed code for the higher level event building. The EUDAQ developers together with WP5

provide examples that cover many of the possibilities. The DataCollector allows, if all information is

provided in the Producers, to successfully build events coming from a mix of externally triggered,

self-triggered or continuously integrating detectors even with different master clocks.

The data collected in the common DataCollector should be sent to the DQM4HEP framework on the

fly to perform the data quality checks. This interface between EUDAQ and DQM4HEP is in

development and is one of the major duties of Task 5.4 of this WP. In recent beam tests, the data was

stored on disk and read out in a quasi-online mode by DQM4HEP. In Figure 1, we show an example

of common online monitoring between a telescope and a high granularity calorimeter (AHCAL [6]

for Linear Collider).


Deliverable: D5.5

Date: 30/11/2017


Figure 1: Diagram of the online event model for DAQ and online DQM.

5. PROOF OF CONCEPT

Several beam test campaigns have provided a testbed for developing and testing the proposed event

model. Specifically, the latest CALICE AHCAL and AIDA beam-telescope combined beam-test

campaign, started at the end of 2016 and ended in February 2017 (at the DESY beamline). This

campaign is considered as a milestone for the event model definition. In the final beam test, four

different devices where tested at the same time providing online synchronized common events from

a mix of externally triggered, self-triggered or continuously integrating detectors running with

different master clocks. Details on the setup and results obtained can be found in the AIDA-2020

MS47 report and in presentations made in the second annual meeting of AIDA2020 [7].


Deliverable: D5.5

Date: 30/11/2017


6. REFERENCES

[1] A. Irles, “Online event data model available”, AIDA-2020 WP5 Milestone 47 report.

http://cds.cern.ch/record/2268256

[2] Y. Liu, “EUDAQ2 User Manual”. Available from

http://eudaq.github.io

[3] LCIO (Linear Collider I/O) event model for linear colliders web page.

http://lcio.desy.de/

[4] DQM4HEP : an online data quality analysis framework for physicists.

https://dqm4hep.github.io/dqm4hep-doc/

R. Ete, T. Coates and A. Pingault, “Data quality monitoring tools ready”, AIDA-2020 WP5 Milestone

47 report.


[5] Telescope DESY webpage (including TLU, telescopes, EUDAQ, etc manuals and documentation)

https://telescopes.desy.de/

D. Cussans, “Description of the JRA1 Trigger Logic Unit (TLU), v0.2c”, Tech. Rep. EUDET-Memo-

2009-04 (2009).

https://www.eudet.org/e26/e28/e42441/e57298/EUDET-MEMO-2009-04.pdf

H. Jansen et al., “Performance of the EUDET-type beam telescopes”, Eur. Phys. J. Tech. and Inst. 3

(2016) 7.

https://doi.org/10.1140/epjti/s40485-016-0033-2

[6] “Analogue HCAL R&D for the ILC detector”.

http://flc.desy.de/hcal/index_eng.html

[7] J. Kvasnicka and K. Krüger, “AHCAL + beam telescope beam test with EUDAQ 2”, AIDA-2020

Annual Meeting 2017. Available from

https://indico.cern.ch/event/590645/contributions/2528376/attachments/1439479/2215366/AIDA20

20_AHCAL_EUDAQ2_20170404.pdf


http://eudaq.github.io/

http://lcio.desy.de/

https://dqm4hep.github.io/dqm4hep-doc/


https://telescopes.desy.de/

https://www.eudet.org/e26/e28/e42441/e57298/EUDET-MEMO-2009-04.pdf

https://doi.org/10.1140/epjti/s40485-016-0033-2

http://flc.desy.de/hcal/index_eng.html

https://indico.cern.ch/event/590645/contributions/2528376/attachments/1439479/2215366/AIDA2020_AHCAL_EUDAQ2_20170404.pdf

https://indico.cern.ch/event/590645/contributions/2528376/attachments/1439479/2215366/AIDA2020_AHCAL_EUDAQ2_20170404.pdf


Deliverable: D5.5

Date: 30/11/2017


ANNEX: GLOSSARY

Acronym Definition

DAQ Data Acquisition System

DQM Data Quality Monitoring

EUDAQ A generic data acquisition framework

LC Linear Collider

LHC Large Hadron Collider

AHCAL Analogue Hadronic Calorimeter technological prototype for the Linear

Collider

SDHCAL Semi-Digital Hadronic Calorimeter prototype for the Linear Collider

EUDET Detector R&D towards the International Linear Collider

LCIO (Linear Collider I/O) is a persistency framework and event data model for

linear collider detector studies

SPS Super Proton Synchrotron at CERN

PODIO Plain-Old-Data objects

DQM4HEP Data Quality Monitoring for High Energy Physics framework

CALICE International High Granularity Calorimetry R&D collaboration

TLU Trigger Logic Unit

ROC Readout Cycle

BIF Beam Interface device