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

2. 2 Run Control Structure M. Gulmini, EDAQ Meeting, Legnaro, February 2009

3. 3 Slow Control and Run Control (Slow) Controlled Component Configuration DB Slow Controller GUI Standalone System RUN CONTROL (Slow Manager) Get State Configuration to load Errors Values to monitor M. Gulmini, EDAQ Meeting, Legnaro, February 2009

4. 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. 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); … … M. Gulmini, EDAQ Meeting, Legnaro, February 2009

6. 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) M. Gulmini, EDAQ Meeting, Legnaro, February 2009

7. 7 Configuration M. Gulmini, EDAQ Meeting, Legnaro, February 2009 (Slow) Controlled Component Configuration DB Slow Controller GUI Standalone System RUN CONTROL (Slow Manager ) Get State Configuration to load Errors Values to monitor 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?

8. 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 M. Gulmini, EDAQ Meeting, Legnaro, February 2009

9. 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!!!! M. Gulmini, EDAQ Meeting, Legnaro, February 2009