[en] MDSplus is a data acquisition system widely used in nuclear fusion experiments. It defines a file format for pulse files and provides a set of tools for data acquisition and management. The whole MDSplus package is used in several fusion experiments to set-up and supervise the data acquisition process. Other experiments use only the data management layer of MDSplus to provide a common format for data exchange between plasma fusion laboratories. HDF5 is a file format and a data access library used by a larger community, mainly outside fusion. HDF5 is used, for example, in earth science research, defense applications and weather services. HDF5 allows managing large and complex data sets and provides a common data format among heterogeneous applications. Both MDSplus and HDF5 support a rich set of data types and a hierarchical data organization, as well as multi-language data access libraries. There are however several significant differences between the two system architectures, making each system better suited in different application contexts. The paper provides a brief overview of the data architectures of MDSplus and HDF5 and analyzes more in detail the peculiar aspects of the two systems. It will be shown that the ranges of applications suitable for the two systems overlap only partially. Finally, some application scenarios will be presented, discussing to what extent each system can provide an optimal solution. This document is composed of an abstract and a poster. (author)

[en] The electronics of the data acquisition system based on silicon photomultipliers is briefly described. The elements and modules of the system were designed and constructed at ITEP especially for the DANSS detector. Examples of digitized signals obtained with the presented electronic modules and selected results on processing of the DANSS engineering data-taking run in spring 2016 are given.

[en] The DZERO experiment located at Fermilab has recently started RunII with an upgraded detector. The RunII physics program requires the Data Acquisition to readout the detector at a rate of 1 KHz. Events fragments, totaling 250 KB, are readout from approximately 60 front end crates and sent to a particular farm node for Level 3 Trigger processing. A scalable system, capable of complex event routing, has been designed and implemented based on commodity components: VMIC 7750 Single Board Computers for readout, a Cisco 6509 switch for data flow, and close to 100 Linux-based PCs for high-level event filtering

[en] The OPAL project (Omni Purpose aparatus for LEP) is presented. It will be a frame and an example to explain the main problems and limitations concerning the mode of event selection, acquisition and information transfer to the final registering system. A quick review of the different problems related to data selection and acquisition is made

No abstract available

[en] Test results on a newly developed Multi-Channel Sample-And-Hold Calorimeter Data Unit (CDU) are presented. The device is organized as 32 input channels, each consisting of four storage cells to take samples of the 32 analog signals at four separate times. The design goals for the development were wide dynamic range and long hold times. Therefore, each storage cell is laid out in a fully differential way and consists of a sampling stage for the signal and another identical stage for a reference voltage. Results on the performance of the device are described

[en] The LHCb read-out uses a set of 320 FPGA based boards as interface between the on-detector hardware and the GBE DAQ network. The boards are the logical Level 1 (L1) read-out electronics and aggregate the experiment's raw data into event fragments that are sent to the DAQ network. To control the many parameters of the read-out boards, an embedded PC is included on each board, connecting to the boards ICs and FPGAs. The data from the L1 boards is sent through an aggregation network into the High Level Trigger farm. The farm comprises approximately 1500 PCs which at first assemble the fragments from the L1 boards and then do a partial reconstruction and selection of the events. In total there are approximately 3500 network connections. Data is pushed through the network and there is no mechanism for resending packets. Loss of data on a small scale is acceptable but care has to be taken to avoid data loss if possible. To monitor and debug losses, different probes are inserted throughout the entire read-out chain to count fragments, packets and their rates at different positions. To keep uniformity throughout the experiment, all control software was developed using the common SCADA software, PVSS, with the JCOP framework as base. The presentation will focus on the low level controls interface developed for the L1 boards and the networking probes, as well as the integration of the high level user interfaces into PVSS. (authors)

[en] A data acquisition system for X-ray free-electron laser experiments has been developed at SACLA. The system was designed for reliable shot-to-shot data storage with a high data stream greater than 4 Gbps and massive data analysis. A data acquisition system for X-ray free-electron laser experiments at SACLA has been developed. The system has been designed for reliable shot-to-shot data storage with a high data stream greater than 4 Gbps and massive data analysis. Configuration of the system and examples of prompt data analysis during experiments are presented. Upgrade plans for the system to extend flexibility are described

[en] We illustrate the performances of the trigger system for the search of cosmic magnetic monopoles, with the streamer tubes of MACRO, for β≥10^-4. (orig.)

[en] The data acquisition system of a large-scale experiment such as UA1, running at the CERN proton-antiproton collider, has to cope with very high data rates and to perform sophisticated triggering and filtering in order to analyze interesting events. These functions are performed by a variety of programmable units organized in a parallel multiprocessor system whose central architecture is based on the industry-standard VME/VMXbus. (orig.)