Use of RCP for Instrument Control Tony Lam 2006 Eclipse SLAC

Outline GumTree  GumTree Demo  GumTree Vista Scientific Eclipse  NOMAD (ILL)  FABLE (ESRF) Collaboration Issues

Problem Domain: Complex Instrument Ecosystem Proposal DB Control System Data Archive Device Drivers Device Server Instrument Server Web Resource Internet GRID Web Service

Solution: Integrated Scientific Experiment Environment Proposal DB Control System Data Archive Device Drivers Device Server Instrument Server Web Resource Internet GRID Web Service cf. IDE

GumTree Project GumTree is a scientific workbench that manages the complete experiment lifecycle for users Integrated Scientific Experiment Environment  Instrument Control & Data Acquisition  Online and Offline Data Analysis  Electronic Laboratory Notebook & Report (OLE, BIRT)  [proposed] Collaborative environment for multi- national experiment (ECF)

Demo 6 minutes demo

GumTree Vista GumTree has been built on a new architecture, with codename Vista GumTree

New Architecture Control System (SICS, EPICS, TANGO) Instrument Model Server GumTree RCP GumTree RAP* Swing Based Diagnostic Tools J2EE Web Interface Batch Server Instrument model definition Project Vista

GumTree Vista Motivation  Data analysis team wants to access experiment data via instrument component  Web interface for status monitoring  Model / data flow driven development GumTree RCP remains its role as the integrated scientific workbench First prototype will be available on Jul ‘06

New Features What can GumTree Vista offer:  Simplified API for adapting to other control system  Stronger security in new layered architecture  Validation of user request based on various sources (eg current instrument status, database, etc)  Multi-clients connectivity (independent of technology choice)

RCP: Control System Controlling instrument via instrument model (JaveBean data structure) Instrument model server can produces a model driven data set Instrument model server can be adapted to other control system

RCP: Visualisation Visualisation component will be split into two levels:  General purpose SWT widget with no dependency on the rest of GumTree system  Extension of GumTree (allows binding with internal GumTree data for display) SWT VISSWT/OpenGL NeXus VIS extends GumTree VIS Can be used by other SWT/RCP applications

RCP: Data Internal data format has been chosen to Extended NeXus format  It describes the whole instrument model  Strong linking to control system, experiment setup (via wizard), monitoring, etc NeXus format can be transformed to other data format via XSLT (heavy commitment by ANSTO’s data analysis team) Another possible GumTree internal data representation: EMF

Data Analysis Run algorithm remotely by RMI, TANGO, Web Service (GRID), or PTP API??

DANSE like simplified scientific workflow

NOMAD Developed by Institut Laue-Langevin (France) To be deployed on 11 neutron beam instruments in June Based on SWT and OpenGL User interface components are generated by XML definition (like XSWT) Has a cool way to perform experiment! Collaboration? Well, it’s not open source.

FABLE Joint collaboration between ESRF (France) and Risø Institute (Denmark) Scientific workbench for crystallography data analysis with synchrotron data Can be extended to acquire data from the synchrotron beamline. Page

Collaboration Share development experience  Discussion  Recommendations Do not duplicate our efforts  Reusable code / plugin Manage existing open source projects

Possible Collaboration Methods Scientific Plugin Library  Every facility requires different system architecture  Sharing codes in plugin level is more realistic  SciForge.net?? Eclipse based scientific community  A community under Eclipse Foundation  Benefits: website space, mailing list, bugzilla, newsgroup, gaining publicity in mainstream IT industry  Drawback: management is time consuming

Case Study on Eclipse Community Model A dedicated scientific eclipse project  Example: Parallel Tools Platform (PTP) Project Managing individual sub-projects under a community  Example: Generative Model Transformer (GMT) Project Promotion of Eclipse technology with almost no software artefacts  Example: Eclipse Community Education Project (ECESIS)

Case Study on Eclipse Community Model Foundation Member Working Groups  Example: Japan Working Group  Should we call ourselves “Scientific Woking Group”?? Initial subproject under existing Eclipse Technology Project  Example: NO  Greg Watson (Los Alamos Cluster computing team) from PTP has offered his help

Conclusion Increasing adoption of Eclipse Technology creates opportunity for us to share codes Question: Are we on the same road?