daq software for the ahcalbib-pubdb1.desy.de/record/292245/files/ahcal_meeting_dic...common daq for...

DAQ software for the AHCAL

Adrian IrlesCALICE AHCAL meeting10th December 2015, DESY (Hamburg)

First and Last Name | Title of Presentation | Date |

Outline of the talk

> AHCAL DAQ hardware (a sketch)

> AHCAL DAQ software

Data taking and detector configuration with Labview

EUDAQ: DAQ for common test beam

> Operation during data taking

Online Monitoring

Quasi online Monitoring

Event building

> Test beam Campaign during 2015

> Prospects

Irles, A. | Calice AHCAL Meeting | 10th Dec 2015


AHCAL DAQ for test beams scalable for ILD

> Controlled by a Labview interface.

> Clock and Control Card (CCC)

Provides master clock; starts and stops the acquisition according to the spill level and readiness of all ASICs; distributes trigger validation

> Link Data Aggregator (LDA)

Packet collecting; packet processing (decoding, merging); send the packets over TCP to DAQ PC

> Detector InterFace (DIF)

Controls the ASICs (voltages, acq. State); collects data from all ASICs on HBU; sends the data to LDA

> ASIC (SPIROC 2b, Omega group)

Reads out 36 SiPMs; has 16 memory channels for ADC and TDCIrles, A. | Calice AHCAL Meeting | 10th Dec 2015

Jiri Kvasnicka | Calice meeting, KEK Tsukuba




> Labview provides very flexible tools to: power the detector (control the MPOD, the rack power supply); set and load the Slow Control Files; Configure the detector and the data taking mode (calibration, beam data); make automated calibration runs; etc





> Labview provides very flexible tools to: power the detector (control the MPOD, the rack power supply); set and load the Slow Control Files; configure the detector and the data taking mode (calibration, beam data); make automated calibration runs; etc


MPOD controller

Main Labview program, Detector Setup tab

http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/LabviewOperation




> Labview provides very flexible tools to: power the detector (control the MPOD, the rack power supply); set and load the Slow Control Files; configure the detector and the data taking mode (calibration, beam data); make automated calibration runs; etc

> Allows to have a very first look of the data while the detector is running Chip by chip information of ADT/TDC

> And the data is saved in ascii format which is useful for online monitoring Channel by channel information of ADC/TDC hit bit etc (discussed in slide 13). Very large file sizes.

> Scintillator AHCAL designed DAQ → we aim for combined testbeams with other sub-detectors

> Complicated tool for test beam shifts (not shifter friendly)



EUDAQ 1.X

> Common DAQ for Linear Collider gets a fresh push in AIDA-2020

EUDAQ1 stable release, Online Monitoring, EUDAQ2 development, mini-TLU

> What is EUDAQ? Is a Data Adquisition (DAQ) framework, modular and portable.

> Originally developped for pixel telescope in the ILC targeted EUDET initiative, since then successfully and widely used by LHC community too

> Central Run Control (commands and status)

> Producer processes configure hardware, read out the data, send it

to the Data Collector.

> The Data Collector receives all the data streams from the

producers and combines them into a single stream.

> Easy and flexible conversion of the raw output data to other formats (i.e. LCIO)



Common DAQ for ILC calorimeters: EUDAQ (1.X)

> First time with different ILC calorimeters running together, Nov-Dec'14 testbeam. Using EUDAQ v1.3.1 and T. Suehara implementations

> The EUDAQ sends the START/STOP commands to the DAQs and collects the data of the different detectors.



Common DAQ for ILC calorimeters: EUDAQ (1.X)

> First time with different ILC calorimeters running together, Nov-Dec'14 testbeam. Using EUDAQ v1.3.1 and T. Suehara implementations

> The EUDAQ sends the START/STOP commands to the DAQs and collects the data of the different detectors.

> Used for almost all 2015 AHCAL test beams

> Labview is used for configuration and to send the data to the EUDAQ

> We keep saving the ASCII files produced by the Labview: two “independent” data files:

Online Monitor



(EU)DAQ for the engineering AHCAL prototype is shifter friendly> Data taking requires just two actions from the shifter: click start or stop button

The EUDAQ sends the start and stop commands.

The Labview is in Listen Mode

> Of course, this is only true if we have set everything before:

System setup, load of the slowcontrol files, voltage supply... etc.

http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/EUDAQOperation



AHCAL raw online monitors

> The first is done directly in the Labview:

General behavior of the detector



AHCAL raw online monitors

> But we also need to check individual channels: ADC spectrum and TDC spectrum

For example for MIP runs where we need to know exactly the position of the beam in our detector.

> This tool uses the ascii files

> Online

> Not event building needed


flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/Monitoring


AHCAL quasi-online monitor: after event building

> New quasi-online monitor: applies reconstruction, MIP calibrations and geometry mapping, at the end of each run.

> Event building is needed (next slide)

Positron (20 GeV) beam, 15 layers, tungsten absorber

flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/Monitoring



Event building from raw LCIO files

> The EUDAQ files (binary, lcio, etc...) store readout frames not events.

> For AHCAL, one readout frame contains several events defined by the BXID (each BXID is separated by 4us)

> The raw data is not sorted according to BXID but according ChipID (in each Chip, the data is sorted by BXID)

> The Event building is done after the run ends.

EUDAQ Raw Data (LCIO)

Readout frame 1

NewLCIO file Event 1

EUDAQ Event Builder processor

EventAHCALCollection

RO 1, BXID 0

Temperature info

Readout cycle 2

RawDataAHCALCollection

...

RawDataAHCALCollectionAll BXID (0 and 1

in this example), all ChipID

Temperature info

Event 2

...


EventAHCALCollection

RO 1, BXID 1


AHCAL 2015 Test Beam Campaign: DAQ performance

http://flcweb02.desy.de/flcwiki/tb2015

> The data is obtained in three different formats:

Text files written by the Labview: large size.

SLCIO files written by the EUDAQ: more manageable size, not compatible with the raw online monitor (yet).

Binary raw files from the bit stream sent to EUDAQ (just for debugging purposes)

> All sets of files are directly uploaded the calice grid (dCache space).

Almost online availability of the data.

> DAQ feedback from Data Quality studies:

Raw online monitoring (still using ASCII files)

New quasi-online monitor: applies reconstruction, MIP calibrations and geometry mapping, at the end of each run.

> DQ from test beam crew based at DESY

Daily study of calibration runs

Full reconstruction analysis.



AHCAL 2015 Test Beam Campaign: DAQ performance

> 3 periods of testbeams at DESY with low energy electrons beams.

February, April: 3 GeV electron beam, 5 big layers in an airstack, the main goal of this testbeam was to get a MIP Calibration for the outer tiles of theses layers.

June: dress rehearsal for CERN testbeams, beam energy scan, running with the EUDET Steel Stack, first try with online monitor and reconstruction

> Two periods at H2@SPS line at CERN (8. – 22. July 2015 and 12. – 26. August 2015)

July '15 (14 Layers, steel absorber) ~660 Runs (of ~20 minutes, 3-5 GB and ~5000 validated events)

August '15 (15 Layers, tungsten absorber) ~480 runs (of ~20 minutes, 3-5 GB and ~5000 validated events)

http://flcweb02.desy.de/flcwiki/tb2015Irles, A. | Calice AHCAL Meeting | 10th Dec 2015


EUDAQ1X AHCAL Implementation during 2015 testbeams: summary> Improved DAQ:

EUDAQ make easy the combined runs (proved with Silicon and Scintillator calorimeters)

We have gain in simplicity for the shifter: you only should care of start/stop and make check the data.

The file size have been reduced and standardized (lcio)

> Issues found during operation (and solved)

The EUDAQ file writing in the LCIO format was very slow in our first implementations. Not a problem during beam data taking due to the beam structure, but made unfordable to make calibration runs with EUDAQ.

This is solved now by the fully integration of the CALICE Producers in EUDAQ (already pulled to the official eudaq repository).



AHCAL DAQ prospects

> To do (short term):

Automatize calibration runs using EUDAQ

EUDAQ Online Monitor:

the online monitor from EUDAQ is designed for pixel detector (x,y, charge plus clusterization and hitmaps)

→ working together with T. Coates and C. Chavez from Sussex that will develop a general Online Monitor (but Calice-oriented) for EUDAQ 1 and 2.

> To do (medium/long term):

Run with a BIF: timestamp the events

Define a common framework for quasi-online event building for testbeams with other detectors.

Move to EUDAQ2

> Synchronous readout (of asynchronous independent subsystems) with a central timestamp distributed by TLU/mini-TLU (Trigger Logic Unit)

> Every Data Stream is stored separately



Back up slides



EUDAQ2: basics


> Every Data Stream is stored separately> The TLU is the central authority for merging> Every event gets compared to the TLU events

to find the corresponding TLU event> The Compare algorithm can easily be modified

by the users. It is part of the converter plugin> Adding the TLU timestamp to the Event> Processing events from different producers

Individually until the tracks are extracted> Merging happens on the level of tracks and not

events

1st EUDAQ Workshop, 24-25 November 2015


EUDAQ2 and the miniTLU

> Successor of the TLU Trigger/Timing Logic Unit

> Hardware developed in AIDA,

Bristol, D. Cussans

> Simple and flexible interface for fast timing and triggering signals.

Can accept or provide a system clock

Accepts asynchronous trigger signals from external sources

→

Converts them in synchronous signals (to send to the device, triggers, etc)

Records timestamps

> Generic design


daq software for the ahcalbib-pubdb1.desy.de/record/292245/files/ahcal_meeting_dic...common daq for...

Documents