1. 14. Oct. 2005 ICALEPCS Geneva EPICS Office1 EPICS Office An Initiative for a new Control System Office Framework Matthias Clausen DESY

2. 14. Oct. 2005 ICALEPCS Geneva EPICS Office2 What is EPICS-Office It is NOT YADM Yet Another Display Manager It is NOT YADCT Yet Another Database Creation Tool It is NOT an Application on it’s own What is EPICS-OfficeWhat EPICS-Office is NOT

3. 14. Oct. 2005 ICALEPCS Geneva EPICS Office3 What is EPICS-Office? It is an environment / framework which enables you to create your control system applications. It shall provide interfaces to: –Control System Data –Control System Name Services –Control System Logging Services –Application Logging Services –Application Management Services –… more It shall provide a generic infrastructure to built pluggable, component based applications: –High level applications (XAL) –User/ operator applications

4. 14. Oct. 2005 ICALEPCS Geneva Control System Office4 The Control System Office Initiative Matthias Clausen DESY

5. 14. Oct. 2005 ICALEPCS Geneva Control System Office5 CSO-Office Motivation The new EPICS Version will provide new features that must be supported also by the applications The existing applications (mainly written in X- Window) run (nearly) only on Unix machines. There are only a few programmers (left) that know how to program X-Window/ Motif The existing applications are similar to the first set of Microsoft applications. They do not share a common look and feel.

6. 14. Oct. 2005 ICALEPCS Geneva Control System Office6 EPICS 4.0 Goals Provide online add/disable of I/O to support continuous operation. Provide redundant control of remote I/O to support improved reliability. Provide name introspection and domain control in support of seamless integration of large control systems Provide triggers, filters, and rate limits to improve resource use of network and client side processing Provide atomic read/write of multiple fields in a record Remove limitations on string lengths, device states, number of input links to support arbitrary sizes/dimension arrays. Record Library to provide pluggable functionality Provide hierarchical devices/ device functionality to support higher level view of application in the front-end processors. Alternate protocols Write with read-back Provide better channel access diagnostics

7. 14. Oct. 2005 ICALEPCS Geneva Control System Office7 Good reasons to think of a new application suite The new EPICS version 4.0 will provide several new features in the IOC and in Channel Access. These will only be available if the clients applications get modified/ rewritten accordingly. The ‚individual‘ look and feel of the existing applications should be changed to a -> Common look and feel Data exchange by objects and not only by name Compile once run ‚in most places‘ Common programming interfaces Application style guidelines Pluggable applications

8. 14. Oct. 2005 ICALEPCS Geneva Control System Office8 The selected Environment Language: Java Development environment (IDE): Eclipse Proposed Rich Client Platform (RCP): Eclipse

9. 14. Oct. 2005 ICALEPCS Geneva Control System Office9 Control System Office Framework My Application EPICS V4 TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback LoggingManage Utility Interfaces

10. 14. Oct. 2005 ICALEPCS Geneva Control System Office10 Control System Office Framework EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces

11. 14. Oct. 2005 ICALEPCS Geneva Control System Office11 Control System Office Framework EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces

12. 14. Oct. 2005 ICALEPCS Geneva Control System Office12 Control System Office Framework EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces

13. 14. Oct. 2005 ICALEPCS Geneva Control System Office13 CSO – Framework Adding Graphics EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces Histogram Graphic Service (GEF) Tex Update Meter Graphic Widgets

14. 14. Oct. 2005 ICALEPCS Geneva EPICS Office14 CSO Interfaces Control System –Data Access –Name Services –Logging Services –Archive Data Utility –Application Logging Services –Application Management Services Trigger Updates, Monitor running CSO Instances, Stop CSO Instance –Record/ Playback –Relational Database Graphic –Graphic Service –Widgets Application/ Application –Drag/ Drop

15. 14. Oct. 2005 ICALEPCS Geneva Control System Office15 My Application CSO – Framework in Eclipse (as a RCP) EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces Histogram Graphic Service (GEF) Tex Update Meter Graphic Widgets MenuHelp

16. 14. Oct. 2005 ICALEPCS Geneva Control System Office16 CSO – Framework Writing Plugins The learning curve for Eclipse plugins is steep Developers which want to write CSO applications must be familiar with the Ecipse plugin ideas Help is needed to increase acceptance -> CSO plugin wizard –Write applications –Write Control System Interfaces –Write Graphic Plugins (widgets)

17. 14. Oct. 2005 ICALEPCS Geneva Control System Office17 CSO – Framework Writing Plugins MenuHelp My EMPTY Application CSO Wizard Application/ Application

18. 14. Oct. 2005 ICALEPCS Geneva Control System Office18 Eclipse Acceptance Widely accepted by industry Last companies to join the Eclipse foundation: Nokia, Compuware Accepted in the EPICS community Accepted at DESY Available through Netinstall at DESY Common interest with TANGO developers and others Eclipse workshop held before ICALEPCS started successfully with 28 participants

19. 14. Oct. 2005 ICALEPCS Geneva Control System Office19 Eclipse Workshop

20. 14. Oct. 2005 ICALEPCS Geneva Control System Office20 Existing Frameworks Presentations during the Eclipse Workshop: Eclipse based archive Viewer by Sergei Chevtsov Gumtree by Tony Lam –Can be called the predecessor of the CSO Framework –CSO developers want to stay in close contact with Tony

21. 14. Oct. 2005 ICALEPCS Geneva Control System Office21 GumTree Platform © Tony Lam

22. 14. Oct. 2005 ICALEPCS Geneva Control System Office22 Upgrade Plan How to upgrade from EPICS V3 to V4? What will happen with all the synoptic displays created on the EPICS sites? => Most of the displays are configured using the existing display tools. The configuration files can be converted into the new format and reused.

23. 14. Oct. 2005 ICALEPCS Geneva Control System Office23 Upgrade Procedure Generic Applications and Configuration- File Converters IOC Core and Database-File Converters EPICS-V3EPICS-V4 Converter DB pluggable CSO components pluggable records drivers (devices)

24. 14. Oct. 2005 ICALEPCS Geneva Control System Office24 EPICS Collaboration < 2003: 150 EPICS user Licenses > 2003: open source

25. 14. Oct. 2005 ICALEPCS Geneva Control System Office25 EPICS Collaboration: It’s the people Collaboration Meeting Archamps 2005 103 Participants 34 Institutes 4 Companies

26. 14. Oct. 2005 ICALEPCS Geneva Control System Office26 Current Status of the Control System Office Working on performance tests X-Window/ AWT / SWT… … to make sure that we are on the right track Working on requirements and use-cases for the CSO-Data Access API

27. 14. Oct. 2005 ICALEPCS Geneva Control System Office27 My Application CSO – Framework Interface Specification: Data Access EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces Histogram Graphic Service (GEF) Tex Update Meter Graphic Widgets MenuHelp

28. 14. Oct. 2005 ICALEPCS Geneva Control System Office28 Current Status of the Control System Office Working on performance tests X-Window/ AWT / SWT… … to make sure that we are on the right track Working on requirements and use-cases for the CSO-Data Access API How we do this -> PO1.063-6 Working on use cases for the Utility Interfaces –First results from drag and drop

29. 14. Oct. 2005 ICALEPCS Geneva Control System Office29 My Application CSO – Framework Interface Specification: Utility EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces Histogram Graphic Service (GEF) Tex Update Meter Graphic Widgets MenuHelp

30. 14. Oct. 2005 ICALEPCS Geneva Control System Office30 Drag and Drop Example

31. 14. Oct. 2005 ICALEPCS Geneva Control System Office31 Architecture Curves Tables EPICS-Gui ServiceManager IDataServiceDataServiceImpl Drag and Drop > Pluggable Components

32. 14. Oct. 2005 ICALEPCS Geneva Control System Office32 Next Steps Finish Control System Data Access API by Christmas this year. (We might also have a look at JAPC from CERN) Finish specification of remaining interfaces in first quarter 2006 First straw man applications middle of 2006 Beta release of EPICS V4 and Control System Office applications by the end of 2006

33. 14. Oct. 2005 ICALEPCS Geneva Control System Office33 Conclusions The EPICS collaboration is taking a major step forward by developing a new major EPICS release. The aim to be ready by end of 2006 also with a new Controls System Office Framework is getting momentum and will most likely be ready in parallel with the new core release. Collecting use cases and requirements is a challenging task, but is necessary for a solid foundation for this new framework.

34. 14. Oct. 2005 ICALEPCS Geneva Control System Office34 EPICS on the Web EPICS Home http://www.epics.org EPICS Version 4 Wiki Page http://www.aps.anl.gov/epics/wiki/index.php/Core_Developer _Pages Control System Office http://epics-office.desy.de Next Collaboration Meeting: 19th June 2004 at Argonne

35. 14. Oct. 2005 ICALEPCS Geneva Control System Office35 The development environment for ALL EPICS-Office developments Eclipse cvs (in the future: Subversion) CodeBeamer CB plugin remote ssh

36. 14. Oct. 2005 ICALEPCS Geneva Control System Office36 Eclipse Plugin Architecture © Toni Lam Plug-in – set of contributions –Example: Python support in Eclipse, including core logic and UI components Extension point - named entity for connecting contributions –Example: Debugging support Extension - a contribution –Example: Python debugging tool