100 likes | 210 Views
Agata DAQ Layout. Gaetano Maron INFN – Laboratori Nazionali di Legnaro. General Overview. Front-end electronic. Data Readout. Slow Control. Trigger. Run Control and Monitor System. Front-end electronic and pre-processing. Event Builder. Pulse Shape Analysis. Ancillary Data Flow.
E N D
Agata DAQ Layout Gaetano Maron INFN – Laboratori Nazionali di Legnaro
General Overview Front-end electronic Data Readout Slow Control Trigger Run Control and Monitor System Front-end electronic and pre-processing Event Builder Pulse Shape Analysis Ancillary Data Flow Agata Data Flow Tracking Storage
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.)
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
Slow Control and Run Control RUN CONTROL Configuration to load Values to monitor Errors Get State GUI Slow Controller (Slow) Controlled Component Configuration DB Standalone System
Controls, Errors and Monitors: the “hooks” of the Sub-Systems GUI GUI Front-end electronic and pre-processing Run Control Login Service Resource Service Pulse Shape Analysis IM. Info / Moni Service (IMS) IM. Top Instrument Manager.(IM) IM. Problem Solver IM. Event Builder IM. IM. IM. Slow Cntr Tracking Ancillary Control Information/errors Storage Monitor
“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
Monitor Hooks 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) e.g. Data Readout Daq application V1 V2 V3 3. Get the selected variables (e.g. Data rate every 2 seconds) e.g. V1 = Data Rate V2 = Error Rate V3 = Buffer Occupancy
Daq application Daq application Daq application V1 V1 V1 V2 V2 V2 V3 V3 V3 • 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 Monitor Subscribers V1 V2 V3 Monitor Collector Monitor Subscribers V4 V5 V6
Maestro Storage IM GUI Resource Service Log Collector Error Collector ….. IM = Function Manager Services Web Services Services Top IM Ancillary IM SlwCtrl IM Narval Systems PSA Chf d’Or Tracking Chf d’Or EVB Chf d’Or SlowCtrl Sub- System Tracking Sub-System PSA Sub-System EVB Sub- System Storage Sub- System Ancillary Sub- System