1. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr CS-Framework - Overview Intro and Overview Status Outlook

2. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Starting Point (  2001) Control System –Control devices (power supplies, function generators, timing, complex experimental procedure…) –No process control (e.g. batch farm) –DAQ and data processing is only a minor issue –Integrate things that were not developed to work together as a system Ever changing set-up –The same experiment is never done twice –Reconfiguration of complete hardware (seconds!) –Integration of new hardware (next beam-time) Small and medium size experiments –No dedicated staff for control systems –Different experiments but similar problems to solve (configuration, complex timing schemes, similar hardware,…) …  What about a “Framework”?

3. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Definition of the CS framework provides features that are commonly needed by many experiments can be maintained be a dedicated and central group allows for exchanging software and know-how saves man power control system = framework + add-ons EE/KS experiment bug reports, new features requested add-ons may become part of framework bug fixes, new features, maintenance

4. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Definition of the CS framework Standardization of components Flexibility: Plugging components together via events Main emphasis: device control, not process control  "It's a kind of toolbox plus some bricks..." Back-end (SCADA, GUI,...) Application layer (sequencer,...) Front-end (devices, drivers,...) Ansatz: "Three-layer architecture" Cycle Control AFG Timing+DAQ HV GUI

5. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Cooking Recipe for the CS Framework One development tool  LabVIEW Standardization  object oriented approach, base classes Distribution to many nodes  DIM (www.cern.ch/dim)www.cern.ch/dim –Event driven communication for everything –Scaling to large systems by distribution –Remote access –… SCADA functionality (alarming, trending, …)  LabVIEW DSC module

6. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Object Orientation (OO) with CS "BaseClass" provides basic functionality (communication layer, active threads,...) "DeviceClass" adds functionality according to specs of device type "DS345". Instantiation: one object per device "BaseClass" "Device Class" inheritance AFG1 AFG2 AFG3 of course: classes for GUIs, Sequencer, State machines,... OO implemented by CS using pure LabVIEW (no LVOOP)

7. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Event Driven Communication DIM (www.cern.ch/dim)www.cern.ch/dim –Peer-to-peer connection, no intrinsic bottle neck –Named service as concept (a name server aids in setting up connections) –“service”: publisher-subscriber-pattern, one-to-many –“command service”: command-pattern, many-to-one CS objects communicate via –DIM services: publishing/subscribing to state information –DIM commands: triggering actions synchronous commands (timeout, “expire date”,…) everybody may talk to everybody Events provide the interface between –device object and it’s GUI object –device object and application layer –hierarchical state machines –… Design Approach - First: communication layer, Second: framework Connectivity to other programming languages and OSs CallerCallee Back-end (SCADA, GUI,...) Middleware (communication,.) Front-end (devices, drivers,...) 3-layers

8. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr PHELIX (Petawatt High-Energy Laser for Heavy Ion Experiments) (slide by S. Götte, GSI) Up to 3 MJ electrical energy converted to 1kJ light energy or 0.5 Petewatt laser power. 2300 documented “shots” (Dec. 2010). About 10k process variables distributed on 15+ nodes in 2 buildings

9. 8-Feb-2012CS-Workshop 2012, Dietrich Beck Quad-Triple Trap Mass Spectrometer ISOLTRAP High-precision mass determination of unstable nuclei with a Penning trap mass spectrometer at ISOLDE/CERN Quad-Triple Trap Mass Spectrometer ISOLTRAP High-precision mass determination of unstable nuclei with a Penning trap mass spectrometer at ISOLDE/CERN www.cern.ch/isoltrap –Nuclear-, Astro-, Fundamental Physics –  m/m  10 -8 (typically!) –via cyclotron frequency of stored ions –“sub-µs ion-juggling” every second

10. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr CS-Framework - Overview Intro and Overview Status Outlook

11. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr SourceForge: downloads, tracker (bugs, features,…)

12. Packaging 28-Feb-2013CS-Workshop 2013, Dennis Neidherr

13. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr SCC via SubVersion @ GSI

14. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Domain Management System: Process Management in a Distributed Environment

15. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Process Monitoring

16. 28-Feb-2013CS-Workshop 2012, Dietrich Beck Documentation via Wiki

17. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Class Documentation via UML Tools

18. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Lessons Learned – What Users say about CS Lessons Learned – What Users say about CS (from a talk by Stefan Götte, at the NI BIG PHYSICS Round Table, Paris, 2009) Stress Field of the Responsible Person: The OS (XP) and/or the intranet are always unreliable, the programming language (LabVIEW) never really fulfills the need, the framework (CS) is only close to the requirement, the classes of other CS collaborators are typically not usable, there is no way to test things since there is no test system available while the real system is always in use, the users never define what the program has to do, but are not pleased with what the programmer delivers, and they misuse the system additionally. Anyhow: The goal is an easy system where the happy user does not realize what happens behind the scene, which works reliable and for ever (better: till the next LabVIEW version is installed).

19. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Lessons Learned – The “Saving-Time-Myth” Wikipedia: “…software frameworks … reducing overall development time” (?) Amount of time for solving a problem decreases dramatically, if a problem may be solved with (generic) existing software. “configuration instead of coding” does not change – but the solution is much better may even increase (short-term), compared to a dedicated solution not (!) using the framework (required: training, courses, understanding and application of conventions) decreases (long-term): framework maintained by others, re- usability of code, replacing hardware, coding conventions enforced, maintainability, common language, know-how transfer, …

20. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Experiments using the CS framework... require high flexibility have a large variety of hardware types have up to 10,000 (1M possible) process variables require fast (  100 ns) timing control using dedicated hardware PHELIX PHELIX Motion CaveA SHIPTRAP ISOLTRAP REXTRAP REXTRAP LEBIT LEBIT GSI, Germany Mainz, Germany Greifswald, Germany CERN, Switzerland MSU, USA Lanzhou, China Jena, Germany Heidelberg, Germany Munich, Germany data taking development commissioning PENTATRAP MLLTrap HITRAP LPT TrigaTRAP ClusterTRAP POLARIS WITCH MATS

21. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr CS-Framework - Overview Intro and Overview Status Outlook

22. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr new classes @ HITRAP Many new classes developed (Magnet-Control with build in software regulation, ISEG PS, etc.) IMAQController to readout IMAQ cameras still some performance issues to solve MCP for ion detection

23. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr new classes @ HITRAP HitrapGUI (based on GOGControllerGUI from Dietrich) Aim is to provide a GUI which is easy to configure and to use Usage is already very easy (good for facilities like HITRAP, where in the end many different physicists will optimize the system for their experiments) The way of configuring this GUI still has to be improved (VI scripting, write a “developer GUI” to configure this GUI?)

24. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Some feature requests from last meeting Minimize CS_Start after start of CS: Not yet implemented (2012 version?) CSDB-Tool - Copy and paste feature: Implemented, but several improvements planned for LV2012 version (here also the question, how many features of this tool are used and if it can be simplified) Variable Delay in DSCIntproc: Delay between creation of shared variables and connecting to DIM services. Implemented, but to find the correct time is now Try-and-Error.

25. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Next Steps Migration to LV 2012 (?): LV2009 is not anymore supported by NI New experiments will not want to use “old” software Some additional features in newer LV versions (LVOOP,...) There are one or two experiments already using versions >2009, but works only in Developer environment, because NI decided to take out an elementary function Our solution will lead to some smaller modifications to all classes (we will try to automatize this via VI scripting) for the user, since the contents.vi´s are now also important in the Developer environment Which classes are needed?  Later

26. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Conclusion and Outlook CS 3.21 released for LV2009. about 15 active applications 1,000,000 PVs demonstrated, an even larger number should be feasible 5,000 objects (  hardware devices) demonstrated, an even larger number should be feasible stability of a distributed CS system is better than a few hundred hours of continuous operation about 15 (60) hardware devices supported on SourceForge (Subversion) FAIR: MATS and parts of HITRAP have selected CS as control system framework.

27. 28-Feb-2013CS-Workshop 2013, Dennis Neidherr Acknowledgements... Holger Brand, Dietrich Beck, Mathias Richter, Alexander Schwinn, Falk Ziegler, Romain Savreux, Chabouh Yazidjian, Klaus Blaum, Dennis Neidherr, Melanie Wolf, Stefan Schwarz, Josh Savory, Stefan Götte, Maximilian Kugler, Tobias Habermann, Michael Block, Frank Herfurth, Christian Rauth, Stephen Koszudowski, Manas Mukherjee, Thomas Rechel, Martin Feldmann, IT@GSI, ……………...