(Original list created by Paul Chu, 22-Feb-2007)

"Should have for version 1" plug-ins:

  1. XAL core as a plug-in
    1. Description: this plug-in is basically converted from xal.jar and can provide XAL accelerator hierarchy, on-line model, tools (optimizer, etc.) and other utilities.
  2. General purpose XML parser plug-in
    1. Description: this plug-in can process any XAL-like XML file and create an (DOM) object, e.g. XAL accelerator description file.
  3. Device "navigator" plug-in
    1. Description: this plug-in can take the (DOM) object created by 2. and form a "tree-like" structure for drill-down purpose.
  4. "probe"-like plug-in
    1. Description: this plug-in will provide general purpose PV info display. It can be linked to 3.
  5. Command line terminal plug-in
    1. Is this desirable?
    2. Description: this plug-in will provide a terminal window within Eclipse (idea stolen from Gumtree).
  6. "scan" plug-in
    1. Description: this plug-in will provide basic "1-D" or "2-D" scan functionality, i.e. scanning one or two PV's and recording any other PV's.
  7. Data correlation plug-in
    1. Description: this plug-in will provide the base for any 2 or 3 PV's correlation measurement. It can be "extended" to many other physics correlation plug-ins.
  8. "Strip-tool"-like plug-in
    1. Description: this plug-in will provide similar functionality as the EPICS strip tool.

"Application-like" plug-ins for version 1:

  1. Wire scanner plug-in
    1. Description: this plug-in will serve as wire scanner application.
  2. Emittance plug-in
    1. Description: this plug-in will serve as emittance application.
  3. Image plug-in
    1. Description: this plug-in will be the same as the Matlab application.

"Other" plug-ins if time allows:

  1. XAL online model plug-in
    1. Description: this plug-in will provide online model execution, result display, etc. It is a replacement for the XAL "MPX" application.
  2. General purpose "knob" plug-in
    1. Description: this plug-in will provide a quick way to combined multiple PV's as a single knob.

"Would be nice to have" items:

  1. An "online model".
  2. Working nicely with CSS (a possible replacement for EDM?)
  3. A "back-end" data storage capability for offline use, e.g. PV Logger in the database.
  4. Posting data/plot to E-log.

Other interesting functionalities also include a good data plotting capability, saving configuration ("remembering" buttons clicked), drag-and-drop among different Eclipse views, easy deployment (distribution/installation/update).

  • No labels

1 Comment

  1. Greg White

    Re: the "should haves" above:

    1. 1 is certainly clear - we would want that. 2 and 3 also.
    2. 4 is obvious too. We would also want an Aida plugin. That's easily done, in fact I already did a simple one though it needs a day or two of work to bring it up to date with Aida's new typeless API.
    3. The command line plugin I'm pretty sure you just get in Eclipse. No work there, and if there is, all one should do is include lauch of an xterm (my Eclipse example already did that, in fact it could lauch xterms on different machines - VMS, AFS flora, the so called "gateways" etc).
    4. 6 and 7 are I think the same thing. if I understand you correctly 6 is just 7 with "time" as the independent variable - just like "Correlation Plots" in the SCP.
    5. 8 wouldn't it be better just to launch striptool? The Eclipse illustration I did included a number of striptoollaunch configs, so you could lauch striptool with some sets of PV preloaded.

    Re: the Application-like plugins. Absolutely, these are our primary objective.

    Re: "Other" plug-ins: ok, sound good.

    Re: "would be nice to have"

    1. we should look closely at 2 - should we in fact base our work on CSS?
    2. posting to e-log. Again, this might be better as a launched application - there is already a TCL app that helps you do that.

    Other plugins that are necessary:

    1. Error logging. This should be based on Err
    2. Scientific plots.