The DAQ system support to the AIV activities of the ASTRI camera proposed for the Cherenkov Telescope Array

(1)

2018

Publication Year

2020-10-21T15:11:55Z

Acceptance in OA@INAF

The DAQ system support to the AIV activities of the ASTRI camera proposed for

the Cherenkov Telescope Array

Title

CONFORTI, Vito; GIANOTTI, FULVIO; TRIFOGLIO, MASSIMO; BULGARELLI,

ANDREA; FIORETTI, VALENTINA; et al.

Authors

10.1117/12.2312131

DOI

http://hdl.handle.net/20.500.12386/27912

Handle

PROCEEDINGS OF SPIE

Series

10707

Number

(2)

PROCEEDINGS OF SPIE

SPIEDigitalLibrary.org/conference-proceedings-of-spie

The DAQ system support to the AIV

activities of the ASTRI camera

proposed for the Cherenkov

Telescope Array

Conforti, V., Gianotti, F., Trifoglio, M., Bulgarelli, A., Fioretti,

V., et al.

V. Conforti, F. Gianotti, M. Trifoglio, A. Bulgarelli, V. Fioretti, O. Catalano, M.

Capalbi, P. Sangiorgi, "The DAQ system support to the AIV activities of the

ASTRI camera proposed for the Cherenkov Telescope Array," Proc. SPIE

10707, Software and Cyberinfrastructure for Astronomy V, 1070724 (6 July

2018); doi: 10.1117/12.2312131

Event: SPIE Astronomical Telescopes + Instrumentation, 2018, Austin, Texas,

United States

(3)

The DAQ system support to the AIV activities of the ASTRI camera

proposed for the Cherenkov telescope array

V. Conforti*

a

, F. Gianotti

a

, M. Trifoglio

a

, A. Bulgarelli

a

, V. Fioretti

a

,

O. Catalano

b

, M. Capalbi

b

, P. Sangiorgi

b

for the CTA ASTRI Project

a

_{INAF OAS Bologna, Via Piero Gobetti 93/3, 40129, Bologna, Italy;}

b

_{INAF IASF Palermo, Via Ugo La Malfa 153, 90146, Palermo, Italy}

ABSTRACT

The Cherenkov Telescope Array (CTA), the next generation ground-based observatory for very high-energy gamma rays, is being built and will be operated by an international consortium. Two arrays will be located in the northern and southern hemispheres. Each telescope array will operate different numbers and types of telescopes. The Italian National Institute for Astrophysics (INAF) is leading the ASTRI (Astrofisica con Specchi a Tecnologia Replicante Italiana) project in the framework of the small size class of telescopes (SST). A first goal of the ASTRI project is the realization of an end-to-end prototype in dual-mirror configuration (SST-2M). The ASTRI camera focal plane is composed of a matrix of silicon photo-multiplier sensors managed by innovative front-end and back-end electronics. The ASTRI SST-2M prototype is installed in Italy at the INAF “M.G. Fracastoro” observing station located at Serra La Nave, 1735 m a.s.l. on Mount Etna, Sicily. The ASTRI Data AcQuisition (DAQ) system acquires, packet by packet, the camera data from the back-end electronics. The packets are then stored locally in one raw file as soon as they arrive. During the acquisition, the DAQ system groups the packets by data type (scientific, calibration, engineering) before processing and storing the data in FITS format. All the files are then transferred to the on-site archive. In addition, we implemented a quick-look component the allows the operator to display the camera data during the acquisition. A graphical user interface enables the operator to configure, monitor and control the DAQ software. Furthermore, we implemented the control panel algorithms within the framework of the Alma Common Software, in order to integrate the DAQ software within the ASTRI control software. The ASTRI DAQ system supports the camera AIV activities and operations. We provide the instrument workstation to support the AIV activities in the laboratory, and the camera server on-site. In this paper, we assess the ASTRI DAQ system as it has performed the AIV tasks for the ASTRI SST-2M prototype. Keywords: data acquisition, camera server, bulk data, ASTRI, Cherenkov telescope array, software engineering, software integration test,

*conforti@iasfbo.inaf.it; phone +39.051.639.8737; http://www.iasfbo.inaf.it/~conforti/

1. INTRODUCTION

The Italian National Institute for Astrophysics (INAF) is leading the ASTRI (Astrofisica con Specchi a Tecnologia Replicante Italiana) project within the ambitious Cherenkov Telescope Array (CTA) [1], the next generation of ground-based observatories for very high-energy gamma-ray astronomy. The goal of the ASTRI [2] project is the realization of an end-to-end Cherenkov Telescope prototype, in dual mirror configuration (2M), with a Cherenkov camera composed of a matrix of silicon photo-multiplier sensors managed by innovative front-end and back-end electronics[3]. The prototype, ASTRI SST-2M, in installed in Italy at the INAF “M.G. Fracastoro” observing station located at Serra La Nave (SLN), 1735 m a.s.l. on Mount Etna, Sicily. Profiting from experience with the prototype, the ASTRI project focusses next on the production of ASTRI telescopes, proposed to be placed at CTA southern site [4]. The ASTRI project includes the Assembly, Integration, and Verification (AIV) plan. The first step foresees the assembly and integration of the camera as a whole in the laboratory. The next step is to integrate the ASTRI camera to the telescope on site. The ASTRI Data AcQuisition (DAQ) [5] system supports the AIV and maintenance activities in the laboratory through an Instrument Workstation. On site, we provide the DAQ system software running on a camera server, which is installed in the server room. Both the Instrument Workstation and the camera server run the same software in different configuration. The ASTRI camera Back End Electronics (BEE) – DAQ interface control document details the interaction between those systems. The DAQ system connects directly the camera BEE and acquires data as a continuous stream of packets. The packet is a discrete unit of raw data. Concerning the data transmission protocol, the DAQ system is compatible with either UDP (User Datagram Protocol) or TCP (Transmission Control Protocol). The DAQ system sorts

Proc. of SPIE Vol. 10707 1070724-1

Downloaded From: https://www.spiedigitallibrary.org/conference-proceedings-of-spie on 01 Oct 2020 Terms of Use: https://www.spiedigitallibrary.org/terms-of-use

(4)

the data packets by data type (scientific, calibration, engineering) using one queue for each type. The complete list of data types is as follows:

1. S21: scientific data only;

2. S22: scientific data with housekeeping; 3. C11: dark stair calibration data;

4. C12: fiber stair calibration data using the internal light pulses generator; 5. C13: dark photo-electron equivalent calibration data;

6. C14: fiber photo-electron equivalent calibration data using the internal light generator; 7. HK: camera housekeeping data;

8. VAR: variance data;

We have defined the measure session as a set of idle and run periods. During the run period, the camera performs calibration and science sessions. In the idle period instead, the camera sends only HK data. The camera is in idle for example at the camera start-up and shutdown, or while the telescope is slewing to acquire at the next target. The DAQ stores the data acquired within one period in one raw file packet by packet. In addition, the DAQ system saves the data in FITS format and stores it one file for each data type. Upon closure, the DAQ system transfers each file to the on-site archive. The DAQ system also provides the quick-look software, which allows the operator to display the camera data during the acquisition. The control panel provides the graphical interface that enables the operator to configure, monitor and control the DAQ software. We implemented this control panel algorithm using the Alma Common Software (ACS) framework in order to integrate the DAQ software within the ASTRI control software. This paper outlines the DAQ system in the context of the ASTRI SST-2M camera AIV activities. The next section details the DAQ system model; section three presents the DAQ software provided during test activities that focused on the user perspective. Section four highlights the DAQ AIV plan in the context of the overall ASTRI AIV plan. The last section discusses the activities that will follow.

2. THE DAQ SYSTEM MODEL

The goal of the DAQ system is to support the ASTRI cameras data acquisition processes. It operates in three main contexts:

1. camera AIV activities; 2. telescope AIV activities;

3. telescope operations for scientific observations; 2.1 The software

During the camera integration and test, the DAQ software is deployed in the Instrument Workstation (IW), which provides the capabilities required to support the development and test activities of the ASTRI camera (see, Figure 1). The DAQ software running on the IW performs the data acquisition and buffering, quick-look and local data storage of the bulk data acquired from the camera BEE, both in raw format (so-called Data Level 0 raw or DL0 raw) and FITS format (DL0 FITS). The local GUI allows the operator to configure, monitor and control the DAQ system.

Proc. of SPIE Vol. 10707 1070724-2

(5)

BEE 1 CAMERA DLO Data Acquisition DLO Camera DAQ Data Display DLO

Data Buffer DLO Data Storage

CAMERA BEE DLO II :I Camera DAQ Data Display À

f

Data Acquisition J DLO DLO Data Buffer J DL() Data Storage ON SITE ARCHIVE I I Data Archive DLO

i

Figure 1 - Logical model of the Instrument Workstation

During the camera integration at the telescope and the telescope operations, the DAQ software is installed on the camera server, in the server room at SLN. The camera server connects directly the camera BEE via optical fiber. The DAQ software running on the camera server provides the same functionalities as the one running on the instrument workstation. The DAQ system interfaces the ASTRI telescope control software [6] through an ACS component. Furthermore, the camera server sends the data files to the ASTRI on-site archive. The camera server can be configured and commanded through the local operator GUI or, remotely, through the telescope control system[7].

Figure 2 - The logical model of the camera server

2.2 The hardware

The hardware makeup of the DAQ system supports compliance with ASTRI specifications, derived from the CTA requirements for the SST telescopes. The DAQ system shall acquire data, packet by packet, from the camera BEE continuously at the minimum data rate 6 MB/s. The DAQ system shall record the whole data packets in raw and FITS format files. During the acquisition, the buffered data shall be accessible in near real-time and in retrieval mode for health monitoring and quick-look purposes. In addition, the DAQ system shall continuously transfer the files to the archive. In order to satisfy those requirements and to effectively support the tests, we selected the following hardware configuration. The instrument workstation is a Case 4U super micro super chassis (Figure 3). The equipment of the instrument workstation is:

 2 CPU Xeon with 6 cores at 2.1 GHz;

 32 GB RAM provided by 4 modules of 8 GB DDR3-1600;

 The RAID SAS/SATA storage provide by the Adaptec 6805 with 8 ports PCI-EX;  2 hard disks (500 GB each) SATA III in RAID 1 for the operating system;  6 hard disks (3 TB) SAS II in RAID 10 for the data storage;

Proc. of SPIE Vol. 10707 1070724-3

(6)

'44

41Fil 7:111

r1t11!

 1 video board PNY Quadro, PCI 2GB DDR5.  2 LAN board, 1Gbit – Intel i350 (Intel pro 1000)

Figure 3 - The instrument workstation

The camera server (Figure 4) is a case 4U super micro chassis. We mounted the camera server on the rack in the server room [8]. The hardware of the camera server consist of:

 2 CPU Xeon with 10 cores at 2.3 GHz;

 64 GB RAM provided by 4 modules of 16 GB DDR3-2133;

 The RAID SAS/SATA storage provided by the Adaptec 6805 with 8 ports PCI-EX;  2 hard disks (1 TB each) SATA III in RAID 1 for the operating system;

 6 hard disks (4 TB each) SAS II in RAID 10 for the data storage;  1 video board PNY Quadro, PCI 4GB DDR5.

 2 LAN board, 1Gbit – Intel i350 (Intel pro 1000)  2 board 10 Gbit SFP

Figure 4 - The camera server

Proc. of SPIE Vol. 10707 1070724-4

(7)

JFX ControlPanelv0.0 CIX

File Configurations Monitor

Camera DAQ CONTROL PANEL

(DAQ discos I] Processors I] Analysis I] TOUR J

Current configuration orgirID: Pmg1D: obulD: RunnD: 402 Configuration Controls J ClearI JEdit Configuration: J SET RUN ID origin id] RUN ID l

> day pipeline] START 11 STOP I] AUTOARCHIVE J

Iprag ial obsbid

The hardware selected and assembled for the camera server and the instrument workstation provides a very powerful, reliable and expandable machine. It supports intensive work from the networking, processing, storage, and display points of view. The hardware has been certified for the operating systems Scientific Linux 6 and 7. The architecture of the hard disks controller allows the operator to perform the hot swap of the hard disks during maintenance activities. The machines also includes the GPUs, not used in the current software version.

3. THE DAQ SYSTEM SOFTWARE

This section details the software component used during the last ASTRI camera AIV activities from the user perspective. 3.1 The control Panel

The camera DAQ control panel is the local GUI, (see Figure 5) that allows the operator to monitor and control the DAQ system. The local GUI provides a user-friendly interface to configure the DAQ software based on the different operation modes of the camera. Furthermore, the user can fully configure the GUI views with customized layouts of buttons and commands, through a web application that stores the active configuration. When the user starts the GUI, the software loads the configuration and displays the desired interface. The local GUI has been implemented in Java and uses the MySQL database management system. This customization feature proved its worth during a test session when we were able to add a new command in a few seconds without modifying any source code.

Figure 5 - ASTRI DAQ local GUI. It allows the operator to configure the measure and run all the acquisition processes. The log panel on the bottom detail the state of any running process.

3.2 The monitor of acquisition and processor components

The activation of the START button in the control panel runs the data acquisition and processor components. The acquisition monitor appears in a new window (Figure 6), which provides details about the incoming packets stream. It displays, for each packet type, the current acquisition rate, the average acquisition rate, the number of packets losts, and the raw- FITS conversion rate. These data are also saved in a log file.

Proc. of SPIE Vol. 10707 1070724-5

(8)

monitor.lnx

Runnin on astrivm MODE' HBR SCOE Powered b INRF CIWS -FW 2014 Run_id HBR: 00293 Date: 14/05/17

i RESULT PATH: /home/csuser/local_dps/share/discos_archive/

i Acquisition Start Time: 22:15:35 Acquisition Stop Time: 22:15:35 is aaaawwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwsaammmaaaaiaakkkkkkwwwwwwwwwwwwwwwwwwwwwwwuiiii

Time: 22:15:35

STATUS: WAIT Connection...

BUF_COUNT: 0 AVG_RATE: -nan BUF_LOST: 0 CUR_RATE: 0.00 TIME_ELAP: 0,00 URG_APID #: 0 TOT_WRG_APID: 0 LAST_CMD: UNKNOWN PROTO_TYPE: UNKNOWN TOT_WRG_VC: 0

ECEIVER ->Data Acquisition V TCP MODE

L r- e11C119q:D]:F-1AF.T]7e1g i itiq-STATUS: MIT to GO BUF ÇOUNT: 0 BUF_LOST: 0 TIME ELAP: 0.00 URG_RPIDu: 0 RRW_FILE:UNKNOWN AVG_RATE: -nan CUR_RATE: 0.00 TOT_WRG_RPID: 0

7 ROVIDER- >DataPROCESSOR Prov V 2 1 64E KEHL TI 3 STATUS: WAIT SHMS Creation

BUF_COUNT: 0 AVG_RATE: -nan BUF_LOST: 0 CUR_RATE: 0,00 TIME_ELAP: 0,00

WRG_APIDw: 0 TOT_WRG_APID :0 BROAD_PORT: INACTIVE BROAD_COUNT: 0 TOT_WRG_CRC: 0 TOT_INV_CRC: 0 RAW_FILE:UMKNOIJN

Usa e /home/csuser/local ds/share/d 10AIL :46606 MatEgg 44

CUR TIME LEFT =00 00:00:00 0 ress <N> for more information

.1 I_ USED STATUS: WAIT to GO BUF_COUNT: 0 BUF_LOST: 0 TIME_ELAP :0,00 RRW_FILE:UNKNOWN AVG_RATE: -nan BUF_RATE: 0,00 101 80( 60( 40C 20( 0 )h Gain histo F' 2D)

ASTRI Camera Quick Look by ASTRI @ IASF Bologna

Eile Qn -Line Off -Line Qptions Predefined Views =lo.. Window

15: 5_PDM High Gain histo

(J 4

!fie Edit View Qptions Tools

r camera I

Vevr c,.:!V c

Sd

"

_{New Single View from Graph Selection}

Full Graph Selection Add Graph to Current Pad

S21 S22 S22 Temperatures C11 C11 Temperatures C12 1,1Z Iemperawret C13 C13 Temperatures C14 C14 HK101 HK101 Temperatures VAR102

o-In_ End data display. Evaluate

)1773- «04(D. » IJ

5PDM High Gain histo (PDM filter)

Help

ins Tools Hel

PDM(0, -1) PDIA Ilgn Gan M1. IPDM1I Ilmrl IAI

1200 1000 RM1 HK101 PDM ID hista PDM triggered histo PDM DAC histo PDM A7T histo PDM CTR histo PDM ERV histo PDM FPB histo PDM RTM histo pnMHVS hictn 600 400 200 III g goo 700 PDM HVI histo PDM DGK histo PDM DGY histo PDM DAC histo (PDM filter) PDM A7T histo (PDM filter) PDM CTR histo (PDM filter) PDM ERV histo (PDM filter) PDM FPB histo (PDM filter) PDM RTM histo (PDM filter) Entries 26048 Mean 982.4 RMS 83.43 ntegral 2.603e +04 1500 1600

Figure 6 - Acquisition monitor. This software details the acquisition of packet in term of acquisition rate, processing rate and percentage of packets lost.

3.3 The quick look

The quick-look tools provide functionality to assess the engineering performance of the ASTRI camera. It accesses the data in near real time during the acquisition (on-line mode), or off-line using the stored data. This software allows the operator to display all the Pixel Detection Modules (PDM) of the ASTRI camera, showing all the logical pixels. The quick look can display the fields of data type in views. This software (Figure 7) displays or saves an image of each view periodically or at the end of the measurement. The user defines the number and the size of views and the graph for each view. Furthermore, the user can select the full mode to display all the acquired data, or the sample mode to get a subset of data with a configurable sampling rate. The user can save the configuration for the future executions.

Figure 7 – The quick look screen. It allows the operator to display the acquiring data through the customizable views.

Proc. of SPIE Vol. 10707 1070724-6

(9)

< alíau 6 9 L O

S

C L 00 uo 6wPUa t p.m uo óulUels IVTO1605t lo po ;poops 00 t00.6e0 '901 10 1 060d mPM OS:L:It OL-00.910Z OS:4L:tt OL-CO-9tOL OS:YL:II (IL-MOM 6ar6LSOT004- t0000C00t0 000 llTSa BTU 1600 MOM'i 10:01:21 OtEOBtOZ 90:6S:tt OS-CO-9102 T0:01:21 0EE0.9102 90:6S:tt OZCO-91Ot MaJ6CS0I00 1-10000-EO0 t0-000u1S0 TTOT 0602 IiìtÔlÄ; OE:Et:it OLEO-Biot t t0:0t:Lt OtE0.910L OC:Ct:Lt OE-E0.810E Lo:ot:tt OL-E08t0í 60r6E50100910000 E00 10 000 u110 LTBT 5600 ::A1YIA1 40:/t:ít 0,E0810L t IC:Et:,t OEE0.810L 40:4t:Lt OL[08100 tE:í1:0I OLCO.BtOt 60J6 450t001t0000000 10 000 u1s0 CTCiT 9640 'wlAl 9L:61:it OL-CO-810L t 50:4I:Lt OLEO.910L 9E:61:Lt OL-E0-1/10L SO:41:E1 00-0-11IOL 601'6 4S0100 tl 1000000010 000u1sv tr9T í640 milAl CO:OL:2t 02-Co9100 I 6Z:61:Zt SRCO-OtOL C0:0i:2t OL-CO.OtOí 6i:6t:2I 02C0-9t0i MW6S50t00 1 í0000-E00-t0-000-u1Se CTBT 8642 I I /ADIA', mom? 9C:1b:ít OL-EoBiOt 6E:t:it OLEOBt02 T t 40:Ot:2t OLE01110L 6E:t4:it 00EO-8t0aL BC:I/:it OZEO-8102 40:OZ:2t 00í0-9t02 6E:1/:Lt 00E0.8t0L 6aJ6 550100 910000 E00-10000 u1s0 6m6 9S0t0O'I c0000EO0-t00o0ulsv OUT 6600 ITV toso :01 aollvuas0o l I '-610.IW! CL:64:Lt OLCO.OtOi t 9C:5:,t 02-[0.8102 C0:64:Lt OZCO.9t0t 90:54:11 00-CO.9t0i maJ6L50100J-10000E001000061s0 9191 ,OS0 :pl wmtaJd '/AIIA, SS:9S:tt 0EC0-0tot t 4L:61:Lt OE-CO-910i SS:95:Lt 0EC09t0t 11:64:Lt 00E09t0í 60J.6-LSOl00i110000E00-t0000u1sv 6'T8T COSL I I 'MPÍÀ: CT:I:Ct 00-[0-9102 T 95:95:21 OL-00-8102 Cl:/t:Ct 02-íO.9102 95:95:21 00-00-9[02 maJ6850100110000 000 10000 u1S0 lSZOT 4050 :OI u10110 PAM I 60:6t:Et OZ-E091ot 41:bt:[I OS-CO-810o 60:6t:Et 0,E081ot 1t:41:Et 02-EO-9t0í 6e1'6850100910000E0010000u1s0 TOOT SOSO !MaIA} 0t:6t:Et 00-E01810t t 0I:6t:Et OL-SO-910, 0t:61:Et OL-00-810L maJ6-650t001t0000E00t0000u1sv LLBY 9050 !miMl 6L:65: OS-CO-010S I LL:55:t 02.00.8t0L 6,:65:It OL008tOi L,:SS:I 0000.8t0i 6e1.6-090100910000001000061sv 0001 L050 : Puv r-melÁ¡ 'mi IIA, L:CO:St 00C01110L 94:CO:St OL-00-010i 1 t OC:65:1,1 OL-00-9t07 94:CO:St 00-00.91o2 L:CO:St 00-00.9I0t OC:6S:4t OLCO-aIOL 9:CO:St 0000910t 6.'6-090100-1-10000-000-10-000-111.0 M12J6-t90t00Yt0000-E00-10-000 ulfe 09T 0050 CUT 6050 vaaMlaq Alep t011lal5 ;sTalA 44:4L:8t 00f0.8102 T BL:It:9t caco-BtOL 40:00:Lt OZE0.810L 9L:1L:Lt OLCO.9tOt OAI'L0o1-000L9oT00

i

10000E00t0000uTS0 9001 Lt50 .m01A 6E:4t:8t OLC081oaL I £E:OL:Bt OZE0-1310L 6E:t:11t OL-EO91ot E0:00:81 0íE0-810L 6'16090100i-10000E001000016S0 0000 115L spl suonanlasqO pu0 wcJOold u16u0 LaS01 as0ild a/nfeaw ag1 uo Ja11U PPE JI A41A', /APIA!! 54:65:9t 02-í0.1110Z 90:6S:9t OL-CO910L O4:4E:91 0,-E0-9100 94:65:91 OL-CO-atOL 54:65:8t 0íE0.8102 04:00:01 0000-9tOt 91:65:91 0200.9I00 60J6,90100910000000100001610 MaJ6E90t001 10000C00t0000u1sv 7091 C IS, 009T i50 sllwll Jaddn pue Jamo, a111 PRIM as00ld alep a01 uo laJlll noA II 06011011 awl' WOO atas tuas aiepuollea5O a1aPPu3 1 a10PLe1S 0weua1ll 4111eeaW PI SS:WW:WI/ pp-ww.AAAA sapgAw :lawlol 051 ul salap 041 Lasul aseald JoA LIMOS

HAI

HD2IV

IdDU'I

VII3[141V3

I2I.LSt

uosa :dnw6 11150

:awewasn alv patto, :so

noA

3.4 The DAQ persistence component

The DAQ acquisition system encompasses the persistence subsystem. This subsystem includes a database, the libraries to interface to the database, and a web application, which supports the acquisition processes. The persistence modules are:

- the web interface for the control panel configuration; - the web interface for the DAQ configuration;

- the “persistenceC” library to support the synchronization among the acquisition processes;

- the “persistenceC++” library to support the synchronization among the conversion raw-FITS processes; - the web interface to display the status of files created upon data arrival.

Figure 8 - Web interface to display the status of the DAQ files.

The web interface depicted in Figure 8, displays the list of files stored in the DAQ system. The user can order the list by measurement session, filename and date. The software also provides filter functionality for searching specific subsets of data. The value in the column “sent” is 1 when the file has been forwarded to the on-site archive, 0 otherwise. The DAQ system includes a daemon configured to send the closed files to the on-site archive during the acquisition process.

4. THE ASSEMBLY INTEGRATION AND VERIFICATION PLAN

We defined the ASTRI DAQ system development plan according to the ASTRI AIV plan [9][10]. The ASTRI camera is a complex instrument where many subsystems must work together to detect the Cherenkov light [11]. The DAQ system interfaces the camera (through the camera BEE and the camera controller) to the on-site archive. We defined the DAQ system integration and verification plan, which presents the overall verification approach, with respect to the requirements, on the ASTRI SST-2M camera DAQ.

The goals in the system integration process are:

 to build the overall software from software items (building logic);  to ensure that the instructions between software items are consistent;

Proc. of SPIE Vol. 10707 1070724-7

(10)

 to ensure that the interactions with external interfaces are consistent;

The ultimate goal of the integration is to deliver the DAQ system that can support the ASTRI camera AIV activities and operations.

4.1 The integration levels

We consider different levels of product integration, corresponding to the architectural principles below:

 The component-level integration. It encompasses all the tasks needed to deliver a component ready for its verification with respect to its technical specification.

 The subsystem/product level integration. It encompasses all the tasks needed to deliver a subsystem ready for its verification with respect to its requirements baseline. It may include specific verification tasks that correspond to the subsystem technical specification.

 The camera BEE - DAQ product integration. It encompasses all the tasks needed to deliver a DAQ version ready for validation.

4.2 The integration plan

According to the integration levels defined in the previous subsection, we defined a plan (Figure 12) to develop, integrate and test the software in different contexts. We developed, tested and verified all the software components. The DAQ_001 version includes the components detailed below.

 DAQ acquisition component that provides:

o acquisition and check of the data stream packet by packet; o the operator GUI;

o the storage of raw files;

o a web based application to configure and retrieve the measurements;  DAQ processor component that provides:

o the conversion if raw to FITS-format packet by packet during the acquisition; o storage of FITS files;

We tested this software version with simulated data. Then we used this software version deployed in the instrument workstation to perform the BEE factory acceptance test (Figure 9). We verified the interface between BEE and DAQ in terms of connection, data packet structure and performance (percentage of packet loss at different bit rates).

Figure 9 - Factory acceptance test.

Then we integrated the software with the quick look and released version DAQ_002. The quick look provides two execution modes:

Proc. of SPIE Vol. 10707 1070724-8

(11)

Camera

data flow

<DAQ_002>

deploy to

Instrument Workstation

ASTRI telescope

Camera

<BEE>

<DAQ_003

deploy to

data flow

monitor and control

SLN sen er room

Y

<

Camera

Server>

onitor and control

CAM CTRL

data flo

on -site archive o off-line: display the measurements contained either in a raw or FITS file;

o on-line: display the measurements in near real time during acquisition;

This software version was deployed in the instrument workstation, which was delivered to Palermo to support the camera tests in the laboratory (Figure 10). In this case, the BEE was into the camera, and the QL displayed the measurements taken with lid closed.

Figure 10 - Camera test in lab.

In the last integration step, we added the archive capabilities to forward the files to the on-site archive. The DAQ ACS components allow the camera controller (CAM CTRL) to monitor and control the DAQ software. The ASTRI camera developer team used the DAQ_003 software version. Furthermore, the camera server at SLN runs the DAQ_003 software version to support the camera AIV activities on-site and operations. In this context, the telescope operates as a whole with the monitoring system support [12], the preliminary science pipeline runs on site [13]. During the first tests, we controlled the camera server through the local GUI. The ACS components are ready for the next test campaigns.

Figure 11 - Camera test on telescope.

Proc. of SPIE Vol. 10707 1070724-9

(12)

DAQ control and data acquisition development,

i

W DAQ acquisition component W i acquisition component verification i DAQ data processing development DAQ processors component W processors component verification V V DAQ acquisition component verified W DAQ processors component verified DAQ QL development DAQ QL component W QL component verification W DAQ QL component verified integration tests DAQ_001_integrated DAQ 001 verification integration tests W DAQ_002_integrated W

(

DAQ archive development DAQ archive component W i archive component verification DAQ archive component verified DAQ_002 verification V DAQ_002 DAQ ACS component development DAQ ACS Component / \ DAQ ACS Component verification V DAQ ACS Component verified LEGEND component development tasks 1 verification tasks product integration tasks work products integration tests W DAQ_003_integrated W DAQ_003 verification V DAQ_003

Figure 12 - DAQ AIV plan.

Proc. of SPIE Vol. 10707 1070724-10

(13)

5. CONCLUSIONS AND NEXT STEPS

We designed and implemented the DAQ system adopting the iterative-incremental approach, in order to provide the required functionality in time for each ASTRI camera AIV milestone. We have performed an assessment of the DAQ system at each step. The DAQ system successfully supported all the camera AIV activities providing the required functionalities at the requested bit rates. During the test sessions, we fixed some bugs not detected during the local tests. In addition, we implemented some new minor features to support the test activities:

- we added to our system’s data transfer protocol based on the TCP/IP (as requested in the ASTRI specification) the UDP connection immediately before the start of the BEE factory acceptance tests;

- we implemented the user logbook software to support the test on-site;

- we added to the control panel the button to check the physical connection between the BEE and the DAQ; - we implemented three acquisition modes, that the user can select at run time, to support many tests on-site:

o TPC/IP: the BEE sends the ASTRI packet through a TCP/IP connection;

o UDP in firmware: the BEE sends the ASTRI packet through multiple UDP datagrams; o UDP in operating system: the BEE sends the ASTRI packet through a single UDP datagram; - we implemented a daemon to automatically send the data files from the DAQ system to the on-site archive; The next step foreseen in the AIV plan is the integration with the ACS components. The ACS software has been locally tested. We will release the next software version after the integration tests on the test bed and eventually on-site.

ACKNOWLEDGMENTS

This work is supported by the Italian Ministry of Education, University, and Research (MIUR) with funds specifically assigned to the Italian National Institute of Astrophysics (INAF) for the Cherenkov Telescope Array (CTA), and by the Italian Ministry of Economic Development (MISE) within the “Astronomia Industriale” program. We acknowledge support from the Brazilian Funding Agency FAPESP (Grant 2013/10559-5) and from the South African Department of Science and Technology through Funding Agreement 0227/2014 for the South African Gamma-Ray Astronomy Programme. We gratefully acknowledge financial support from the agencies and organizations listed here: http://www.cta-observatory.org/consortium_acknowledgments.

REFERENCES

[1] Vercellone, S., et al., The CTA Consortium, “The next generation Cherenkov Telescope Array observatory: CTA”, Nuclear Instruments and Methods in Physics Research A 766 (2014) 73–77 (2014).

[2] Maccarone, M.C., et al., for the CTA ASTRI Project, “ASTRI for the Cherenkov Telescope Array”, Proc. 3535 ICRC, 12-20 July 2017, Busan, South Korea, PoS(ICRC2017)855.

[3] Catalano, O. et al., for the CTA ASTRI Project, “The ASTRI camera for the Cherenkov Telescope Array”,

these proceedings SPIE (2018).

[4] Scuderi, S. et al., for the CTA ASTRI Project, “From the Etna volcano to the Chilean Andes: ASTRI end-to-end telescopes for the Cherenkov Telescope Array”, these proceedings SPIE (2018).

[5] Conforti, V., et al., for the CTA ASTRI Project, “The Camera Server of the ASTRI SST-2M Telescopes proposed for the Cherenkov Telescope Array”, Procs. 25th ADASS, 25 - 29 October 2015, Sydney, Australia. [6] Antolini, E., et al., for the CTA ASTRI Project, “Telescope Control System of the ASTRI SST0-2M prototype

for the Cherenkov Telescope Array”, Proc. ICALEPS, 8-13 October 2017, Barcelona, Spain, Paper THMPL04. [7] Conforti, V., et al., for the ASTRI collaboration and CTA consortium, “The high-level interface definitions in

the ASTRI/CTA Mini Array Software System (MASS)”, Proc. ADASS XXIV, Calgary, Canada, 5-9 October 2014, At Calgary.

Proc. of SPIE Vol. 10707 1070724-11

(14)

[8] Gianotti, F., et al., for the CTA ASTRI Project, “Information and Communications Technology (ICT) Infrastructure for the ASTRI SST-2M telescope prototype for the Cherenkov Telescope Array”, Proc. SPIE Astronomical Telescopes + Instrumentation 2016, Paper No. 9913-137.

[9] Stringhetti, L., et al., “The Verification Process in the ASTRI Project: the Verification Control Document (VCD) Array”, Proc. INCOSE-CIISE 2014, CEUR-WS, Vol 1300, 22 November 2014, Pages 106-115.

[10] Conforti, V., et al., for the CTA ASTRI Project, “Procedures of Software Integration Test and Release for ASTRI SST-2M Prototype proposed for the Cherenkov Telescope Array”, Proc. ICALEPS, 8-13 October 2017, Barcelona, Spain, Paper TUPHA004.

[11] Sangiorgi, P., et al., for the CTA ASTRI Project, “The software architecture of the Camera for the ASTRI SST-2M prototype for the Cherenkov Telescope Array”, Proc. SPIE Astronomical Telescopes + Instrumentation 2016, Paper No. 9913-120.

[12] Gianotti, F. et al., for the CTA ASTRI Project, “The ACS-OPC UA based ICT monitoring system of the ASTRI SST-2M prototype proposed for the Cherenkov Telescope Array”, these proceedings SPIE (2018).

[13] Lombardi, S. et al., for the CTA ASTRI Project, “ASTRI data reduction software in the framework of the Cherenkov Telescope Array”, these proceedings SPIE (2018).

Proc. of SPIE Vol. 10707 1070724-12