Presentation is loading. Please wait.

Presentation is loading. Please wait.

24. March 2006 SLAC Workshop Control System Studio1 CSS Control System Studio Report on the current state Matthias Clausen DESY.

Similar presentations


Presentation on theme: "24. March 2006 SLAC Workshop Control System Studio1 CSS Control System Studio Report on the current state Matthias Clausen DESY."— Presentation transcript:

1 24. March 2006 SLAC Workshop Control System Studio1 CSS Control System Studio Report on the current state Matthias Clausen DESY

2 24. March 2006 SLAC Workshop Control System Studio2 Today’s CSS Presentstion How CSS started What we wanted to do (slides from ICALEPCS presentation) What we have achieved Next steps

3 24. March 2006 SLAC Workshop Control System Studio3 Short History The Control System Studio initiative started in May 2005 during the EPICS workshop at SLAC –At this time it was still called ‘EPICS-Office’ –The basic ideas are still the same but the focus has been changed from EPICS centric to Control System openness. –During ICALEPCS’05 in Geneva the name changed from EPICS Office to Control System Studio. –The current developments are driven mainly by DESY Specifying fundamental interfaces (control system data API) Specifying and testing mandatory interfaces (naming/ logging…)

4 24. March 2006 SLAC Workshop Control System Studio4 What is the Control System Studio? It is (is going to be) an environment / framework which enables you to create your control system applications. It will provide interfaces to: –Control System Data –Control System Name Services –Control System Logging Services –Application Logging Services –Application Management Services –… more It will provide a generic infrastructure to built pluggable, component based applications: –High level applications (XAL) –User/ operator applications

5 24. March 2006 SLAC Workshop Control System Studio5 CSS (initial) 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 24. March 2006 SLAC Workshop Control System Studio6 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

7 24. March 2006 SLAC Workshop Control System Studio7 EPICS-V4 Status.. as of now(March 2006) Due to lack of manpower (and some ‘internals’) the current developments of EPICS-V4 have made only slow – but constant - progress over the last months. The design of the CSS-DataAccess API is contracted by DESY to Cosylab. –The ongoing work is coordinated with the V4 core team. This way we can make sure that the new API will be conformant with the current EPICS-V4 design Two contracts with industry to develop a Redundancy Monitor Task and for the Redundancy Continuous Control Executive are under way. First implementations – independent from Epics-V4 due in May’06

8 24. March 2006 SLAC Workshop Control System Studio8 The selected Environment Language: Java Development environment (IDE): Eclipse Proposed Rich Client Platform (RCP): Eclipse

9 24. March 2006 SLAC Workshop Control System Studio9 Control System Studio Framework My Application EPICS V4 TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback LoggingManage Utility Interfaces

10 24. March 2006 SLAC Workshop Control System Studio10 Control System Studio Framework EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces

11 24. March 2006 SLAC Workshop Control System Studio11 Control System Studio Framework EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces

12 24. March 2006 SLAC Workshop Control System Studio12 Control System Studio Framework EPICS V4 My Application TANGO EPICS V3 Control System Interfaces LoggingArchiveName Record Playback Logging Manage Utility Interfaces

13 24. March 2006 SLAC Workshop Control System Studio13 CSS – Framework Adding Graphics (initial design) 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 24. March 2006 SLAC Workshop Control System Studio14 CSS 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 CSS Instance –Record/ Playback –Relational Database Graphic –Graphic Service –Widgets Application/ Application –Drag/ Drop

15 24. March 2006 SLAC Workshop Control System Studio15 My Application CSS – Framework in Eclipse (as an 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 24. March 2006 SLAC Workshop Control System Studio16 CSS – Framework Writing Plugins The learning curve for Eclipse plugins is steep Developers which want to write CSS applications must be familiar with the Ecipse plugin ideas Help is needed to increase acceptance -> CSS plugin wizard –Write applications –Write Control System Interfaces –Write Graphic Plugins (widgets)

17 24. March 2006 SLAC Workshop Control System Studio17 CSS – Framework Writing Plugins MenuHelp My EMPTY Application CSO Wizard Application/ Application

18 24. March 2006 SLAC Workshop Control System Studio18 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 24. March 2006 SLAC Workshop Control System Studio19 Eclipse Workshop

20 24. March 2006 SLAC Workshop Control System Studio20 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 CSS Framework –CSS developers want to stay in close contact with Tony

21 24. March 2006 SLAC Workshop Control System Studio21 GumTree Platform © Tony Lam Best Open Source RCP Application Congratulation to Tony For the Eclipse Award !!!

22 24. March 2006 SLAC Workshop Control System Studio22 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 24. March 2006 SLAC Workshop Control System Studio23 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 24. March 2006 SLAC Workshop Control System Studio24 Where are we now? In order to make the right/ reasonable decisions for the future we are not focusing on writing applications. Writing so called ‘Spikes’ we can test certain functionalities to find out what works, how – and why?

25 24. March 2006 SLAC Workshop Control System Studio25 Current CSS Status Internal Interfaces (I) CSS Drag and Drop Drag an object (with it’s data) from one CSS view (application) into another view (application). From the synoptic display (stripchart) into the data analysis tool. The proof of principle has been shown in a ‘spike’.

26 24. March 2006 SLAC Workshop Control System Studio26 My Application EPICS V4 My Application TANGO EPICS V3 LoggingArchiveName Record Playback Logging Manage MenuHelp Current CSS Status Internal Functions (I) My Application EPICS V4 My Application TANGO EPICS V3 LoggingArchiveName Record Playback Logging Manage Histogram Graphic Service (GEF) Tex Update Meter MenuHelp Drag and drop

27 24. March 2006 SLAC Workshop Control System Studio27 Current CSS Status Control System Interfaces (I) CSS Data Access API: Phase-I –Collecting requirements – finished Phase-II –Writing Specification – in progress CSS Data Access Introspection interface and CSS Naming Service Collecting ideas/requirements for LDAP implementation

28 24. March 2006 SLAC Workshop Control System Studio28 My Application CSS – 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

29 24. March 2006 SLAC Workshop Control System Studio29 My Application CSS – 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

30 24. March 2006 SLAC Workshop Control System Studio30 Current CSS Status Control System Interfaces (II) CSS Message Interface(s) Collecting Messages –Java Message Service is the specification/ OpenJMS is the implementation we use –Forwarding messages through filters to: SMS Server √ Oracle database Files Receiving (online) Messages –Hooking up to an OpenJMS Message Queue. Throttling the data flow hrough Message Filters Reading (offline) Messages –Query to Oracle database –Reading files

31 24. March 2006 SLAC Workshop Control System Studio31 My Application CSS – Framework Interface Specification: Logging 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

32 24. March 2006 SLAC Workshop Control System Studio32 The Message System built on OpenJMS

33 24. March 2006 SLAC Workshop Control System Studio33 Current CSS Status Control System Interfaces (II) CSS Archive Interface Based on Sergei’s interface of the Java Archive Viewer Must be compatiple with DESY’s Archive API (AAPI)

34 24. March 2006 SLAC Workshop Control System Studio34 My Application CSS – Framework Interface Specification: Archive 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

35 24. March 2006 SLAC Workshop Control System Studio35 Current CSS Status Utility Interfaces (I) CSS Message Interface (in applications) √ Generating and sending (log) messages from applications –First implementation in Eclipse-RCP plugin available –Output can be configures to write to: Eclipse console File OpenJMS server

36 24. March 2006 SLAC Workshop Control System Studio36 My Application CSS – 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

37 24. March 2006 SLAC Workshop Control System Studio37 The EPICS Alarm Message Scheme IOC push (any) monitor (selected) message queue filter RDB filter alarm viewer filter actions alh cfg log display actions user-mode system-mode

38 24. March 2006 SLAC Workshop Control System Studio38 Current CSS Status Utility Interfaces (II) CSS Management Interface Management of multiple instances of running CSS applications –CSS applications by default cannot use the update mechanism Make sure that the CSS instance is running a well tested version ( Eclipse-version; plugin versions) –CSS updates can be triggered by the (remote) CSS manager Allowing updates only during maintenance days –Sending stack traces to management console –Remote help for local operator (the collaboratory approach) Instant messaging Synchronizing individual Eclipse views via vnc Eclipse Communication Framework (ECF) is a hot candidate Unsolved: Authentication/ Authorization

39 24. March 2006 SLAC Workshop Control System Studio39 My Application CSS – 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

40 24. March 2006 SLAC Workshop Control System Studio40 Current CSS Status Utility Interfaces (III) CSS Record/ Playback Interface Recording and Playback of operator actions –Recording all the actions necessary to stat a machine –Recording the tuning of the machine –Record and playback for operator training Eclipse Test and Performance Tools Platform (TPTP) is a hot candidate TPTP recording can also be used to test the graphical applications (JUnit does not work here) Unsolved: running RCP mode (not only IDE)

41 24. March 2006 SLAC Workshop Control System Studio41 My Application CSS – 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

42 24. March 2006 SLAC Workshop Control System Studio42 New Requirements Built in documentation & help √ International Language Support Writing CSS properties in XML √ Providing JUnit Tests for each plugin √ Preparing Ant scripts for nightly builds

43 24. March 2006 SLAC Workshop Control System Studio43 Lessons learned Do not mix Eclipse 3.1 with 3.2-M5 Make sure you have a ‘clean’ workbench Take care of dependencies with other packages …

44 24. March 2006 SLAC Workshop Control System Studio44 Open Questions Which implementation will be used for graphic displays? SWT JFace Draw2d GEF -> Tendency: SWT Checking out: How is GEF/ draw2d implemented

45 24. March 2006 SLAC Workshop Control System Studio45 New Answers from EclipseCon BIRT is THE reporting tool –Alarm-Histrory –IOC Configuration It’s easy to run Eclipse PCP (Poor Client Platform) -> headless Eclipse –Writing all of you applications as plugins Run in RCP or PCP mode! –Example: Message filters

46 24. March 2006 SLAC Workshop Control System Studio46 The Message System built on OpenJMS

47 24. March 2006 SLAC Workshop Control System Studio47 Next Steps Finish Control System Data Access API before June Writing ‘Spikes’ for the graphical user interface –In SWT –In draw2d Finish specification of remaining interfaces in second quarter 2006 First straw man applications middle of 2006 ?June 2006?

48 24. March 2006 SLAC Workshop Control System Studio48 CSS on the Web Control System Studio http://css.desy.de Mailing-List Epics-office@desy.de Software Lifecycle Management (Codebeamer): http://elogbook.desy.de:8081/cb Sources available in cvs repository at DESY (You’ll need a DESY account) EPICS Version 4 Wiki Page http://www.aps.anl.gov/epics/wiki/index.php/Core_Developer_Pages

49 24. March 2006 SLAC Workshop Control System Studio49 The development environment for CSO developments Eclipse cvs (in the future: Subversion) CodeBeamer CB plugin remote ssh


Download ppt "24. March 2006 SLAC Workshop Control System Studio1 CSS Control System Studio Report on the current state Matthias Clausen DESY."

Similar presentations


Ads by Google