1 / 9

Run Control and Slow Control

Run Control and Slow Control. Agata EDAQ Meeting Legnaro, 19/02/2009. Run Control Structure. Slow Control and Run Control. RUN CONTROL (Slow Manager). Configuration to load. Values to monitor. Errors. Get State. GUI. Slow Controller. (Slow) Controlled Component. Configuration DB.

donnel
Télécharger la présentation

Run Control and Slow Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Run ControlandSlow Control Agata EDAQ Meeting Legnaro, 19/02/2009

  2. Run Control Structure

  3. Slow Control and Run Control RUN CONTROL (Slow Manager) Configuration to load Values to monitor Errors Get State GUI Slow Controller (Slow) Controlled Component Configuration DB Standalone System

  4. Slow Control and Run Control (II) • Slow Control Components: • Digitizers (MIDAS) • Core/Segment Mezzanines (ENX) • Carrier boards • GTS • The Slow Control Subsystems are “standalone systems”, with their own configuration DB/files, GUI, … • The Run Control structure foresees one “Slow Control Manager” per “Controlled Component” • SOAP/HTTP communication protocol • Each slow control component should provide a web service (described by a WSDL) • Each slow control can act as a web service client to report errors to the Run Control

  5. Agata Slow Control WSDL • Agata Slow Control WSDL (V. Pucknell) int Do-Reset (int *rc);int Do-SetUp (int *rc);int Do-Stop (int *rc);int Do-Go (int *rc);int Get-State (int *rc, int *code, char *state, char *reason);int Get-Counters (int *rc, char *counters);int Get-Rates (int *rc, char *rates); <definitions name="DataAcquisitionControlServer" targetNamespace="http://npg.dl.ac.uk:8015/DataAcquisitionControlServer.wsdl"> … <message name="Get-StateRequest"> </message> <message name="Get-StateResponse"> <part name="ResponseCode" type="xsd:int"/> <part name="Code" type="xsd:int"/> <part name="State" type="xsd:string"/> <part name="Reason" type="xsd:string"/> </message> …

  6. Agata Slow Control WSDL (II) • This WSDL is implemented for the digitizers and for the core/segment mezzanines • A prototype Slow Control Manager (Slow Control WSDL client) has been implemented and integrated in the Run Control hierarchy • Preliminary tests with MIDAS and ENX were successful • Further tests in a real/realistic environment are necessary • Is the “slow control” WSDL good enough? Or it needs extensions? • Are there dependencies between slow control subsystems and daq to take into consideration? • i.e.: trigger is always started last and stopped first, … • Need to implement the proper actions in the run control code (Top Manager)

  7. Configuration RUN CONTROL (Slow Manager) Configuration to load Get State Errors Values to monitor GUI Slow Controller (Slow) Controlled Component • Each subsystem has its own way to manage configurations • The Run Control uses the Resource Service DB for its own configuration • configurations of the controlled components might also be stored; a configuration change in a subsytems force to store a new config (for all Agata) in the RS DB • How the shifter chooses the overall Agata configuration for a data taking run? • How the Run Control manages the configurations? Configuration DB Standalone System

  8. Configuration (II) • We propose to use the concept of Global Configuration Key (a Name) • A limited amount of Keys should be available to the shifter in the main GUI • i.e: TRIPLE_CLUSTER, TEST_EVB, FEB_SOURCE_TEST, … • Subsystem experts associate the Global Configuration Keys to the proper configuration to load • The Run Control managers dispatch the Configuration Key received by the GUI to the subsystems (Configure Command) • Subsystems translate the Key in the proper configuration to load • Agata Slow Control WSDL should be extended in order to have the Key as input parameter at Configuration/Setup time

  9. Summary / To do… • All Slow Control Subsystems need to implement the proposed Agata Slow Control WSDL • Extensions to the present WSDL necessary? • Identify dependencies between the several Agata subsystems (daq and slow) in order to implement the proper control actions in the Run Control • Overall Agata Configuration • Global Configuration Key • Integrate all the subsytems in the Run Control structure • Integration tests, … , make experience!!!!

More Related