G. Maron, Agata Week, Orsay, January Agata DAQ Layout Gaetano Maron INFN – Laboratori Nazionali di Legnaro

G. Maron, Agata Week, Orsay, January General Overview Run Control and Monitor System Slow Control Event Builder Tracking Storage Pulse Shape Analysis Front-end electronic and pre-processing Data Readout Front-end electronic Trigger Agata Data Flow Ancillary Data Flow

G. Maron, Agata Week, Orsay, January Run Control Main Tasks Access to the Agata data acquisition system (login) Configure the daq –Select the partition to run (i.e. a gts partition, enable/disable ancillary, etc.) –Run multiple partition (e.g. calibration mode) Synchronize other sub-system (e.g. slow control, trigger, ancillary, etc.) to be configured Control the overall system (e.g. start, stop, etc.) Handle all the information (e.g. generic log) and error/state messages –Show (e.g. alarms) –Archive (history) –Handle the error in some automatic way (e.g. expert system) to help to fix malfunctioning Monitor the DAQ (e.g. data rate, error rate, etc) Provide access to the GUIs Provide tools to help the cooperation for people in shift (e.g. logbook, chat, videoconference, etc.)

G. Maron, Agata Week, Orsay, January Slow Control Main Tasks Main Slow Controlled Components –Agata Global Trigger –Agata Front End Electronics –Agata Pre-Processing –Ancillary Front End Electronics –... Slow Control main tasks –Store (DB) hardware configurations –Load a given configuration –Monitor the component –Handle error/alarm events and pass them to the Run Control

G. Maron, Agata Week, Orsay, January Slow Control and Run Control (Slow) Controlled Component Configuration DB Slow Controller GUI Standalone System RUN CONTROL Get State Configuration to load Errors Values to monitor

G. Maron, Agata Week, Orsay, January GUI Front-end electronic and pre-processing Pulse Shape Analysis Event Builder Tracking Storage Control Information/errors Monitor Ancillary Slow Cntr GUI Resource Service Login Service Info / Moni Service (IMS) Top Instrument Manager.(IM) Run Control Problem Solver IM. Controls, Errors and Monitors: the “hooks” of the Sub-Systems

G. Maron, Agata Week, Orsay, January “Hooks” definition General –The sub-systems hooks should be an interface as much as possible homogeneous between the different systems. This help the task of the top IM. –Some effort should be put in this phase to define these interfaces Hooks –Controls Send commands and receives back a status Set and get parameters –Errors Send log information and errors. Errors are sent asynchronously –Monitor A publish/subscribe mechanism should be used to select the variables to monitor

G. Maron, Agata Week, Orsay, January Monitor Hooks Daq application e.g. Data Readout V1 V2 V3 1. Publish the variables that can be published (defined at the code level of the application) 2. Brows the variables you want to monitor (e.g. Data rate) 3. Get the selected variables (e.g. Data rate every 2 seconds) e.g. V1 = Data Rate V2 = Error Rate V3 = Buffer Occupancy

G. Maron, Agata Week, Orsay, January Every DAQ node should have the monitor hooks Monitor Collector nodes should be defined in order to have summary views of the sub-system of part of it Daq application V1 V2 V3 Daq application V1 V2 V3 Daq application V1 V2 V3 Daq application V1 V2 V3 Monitor Collector V4 V5 V6 Monitor Subscribers Monitor Subscribers

G. Maron, Agata Week, Orsay, January Top IM GUI Services Services PSA Chf d’Or EVB Chf d’Or Tracking Chf d’Or Storage IM SlwCtrl IM EVB Sub- System Storage Sub- System PSA Sub-System Tracking Sub-System SlowCtrl Sub- System Maestro IM = Function Manager Web Services Resource Service Log Collector Error Collector ….. Ancillary IM Ancillary Sub- System Narval Systems