Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Triquetrum/ICE

Part of the Triquetrum Project is to interface with ICE. This page describes how to set up ICE and Triquetrum.

This work is very speculative and is for reference by Triquetrum developers. It probably won't be of much use for other people.

What is this about

Currently the focus is on enabling ICE to select and launch Triquetrum workflows. We're not yet going for a full integration of the workflow editor in ICE, but this would be the natural next step.

Exporting Features from Triquetrum

ICE requires features from Triquetrum. Eventually, we will have a P2 site for these features, but in the near term, we export the features by hand from a Triquetrum workspace.

  1. See Building From Sources for how to setup a workspace and how to build Triquetrum in Eclipse.
  2. Select 3 features in your workspace :
    1. org.eclipse.triquetrum.core.feature
    2. org.eclipse.triquetrum.ptolemy.feature
    3. org.eclipse.triquetrum.workflow.core.feature
  3. File -> Export
  4. In the Export window:
    1. Plug-in Development -> Deployable features
    2. Click Next
  5. In the Deployable Features window:
    1. In "Directory", browse to a directory, which will be used in the ICE RCP in the next section
    2. In the Options tab, select "Package as individual JAR archives", "Generate p2 repository" and "Use class files compiled in the workspace". Optionally you can also "Export source" as "Generate source bundles".
    3. Click Finish.
  6. In the selected directory you should see the typical p2/install directory structure.
    1. In the features folder the 3 selected features should be present
    2. In the plugins folder you should have 31 plugins when you exported Triquetrum sources as well.
delerw@DELERW-PC /c/temp/triquetrum/features-for-ice
$ ls
artifacts.jar  content.jar  features  plugins
delerw@DELERW-PC /c/temp/triquetrum/features-for-ice
$ cd plugins
delerw@DELERW-PC /c/temp/triquetrum/features-for-ice/plugins
$ ls
diva_11.0.0.201602222155.jar
org.eclipse.triquetrum.common.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.common_1.0.0.201602271915.jar
org.eclipse.triquetrum.processing.api.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.processing.api_1.0.0.201602271915.jar
org.eclipse.triquetrum.processing.model.impl.memory.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.processing.model.impl.memory_1.0.0.201602271915.jar
org.eclipse.triquetrum.processing.service.impl.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.processing.service.impl_1.0.0.201602271915.jar
org.eclipse.triquetrum.validation.api.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.validation.api_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.actor.ui.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.actor.ui_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.api.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.api_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.execution.impl.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.execution.impl_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.model.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.model_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.repository.impl.filesystem.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.repository.impl.filesystem_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.ui.source_1.0.0.201602271915.jar
org.eclipse.triquetrum.workflow.ui_1.0.0.201602271915.jar
org.ptolemy.commons_11.0.0.201602222155.jar
ptolemy.actor.lib.gui_11.0.0.201602222155.jar
ptolemy.actor.lib_11.0.0.201602222155.jar
ptolemy.core_11.0.0.201602222155.jar
ptolemy.domains.process_11.0.0.201602222155.jar
ptolemy.domains.sdf_11.0.0.201602222155.jar
ptolemy.gui_11.0.0.201602222155.jar
ptolemy.moml_11.0.0.201602222155.jar
delerw@DELERW-PC /c/temp/triquetrum/features-for-ice/plugins
$ ls -l *.jar | wc -l
     31

Setting up ICE

Below are instructions on how to set up the ICE application that will run Triquetrum workflows.

This is based on a fork of the main ICE repo.

This is very likely to change or otherwise not work in the future.

Jay prepared a skeleton for a org.eclipse.ice.triquetrum.model.TriquetrumWorkflowItemModel in a bundle org.eclipse.ice.triquetrum. This was done by using the ICE project generator. A more sustainable way would be to leverage upcoming changes to the ICE workflow engine which makes it possible to compose workflow engines.

  1. Create an empty workspace
  2. Get the fork from https://github.com/jayjaybillings/ice-triquetrum
  3. Switch to the next branch and import all the projects.
  4. Go to "org.eclipse.ice.target.mars" and :
    1. In the mars.target Target Definition tab under the list of Locations, click on the location "file:/C:/temp/triquetrum/features-for-ice", then click on Edit
    2. In the Edit window, click on Add and then Local, then browse to the Triquetrum Features exported above. Click on Open, then OK.
    3. In the Edit Content window, under Names will appear "There are no categorized items". The fix is to un-check "Group by Category", which will show all the Triquetrum features. Click on Select All, there should be 6 in total. Check the checkbox to Include required software is on and then Finish.
      1. FIXME: Christopher has 3 names, each duplicated (see below). Is this correct? TriquetrumIceTargetDefinitionPane.png
      2. Yep, that's it. Erwin still has to figure out how exported source features can be shown with a different name, but for the moment binaries and sources have duplicated feature names unfortunately.
    4. In the bottom right of the ICE Eclipse window a message about "Resolving Target Definition" will appear. Let the target resolve, this may take a long time. The Triquetrum entry should show 81 plug-ins available.
      1. FIXME: See above, Christopher had only 70 plugins?
      2. RETEST: this should be ok after you've added the two missing triq bundles as described above? (which should result in some additional deps bundles in here as well to reach 81)
    5. In the mars.target pane, click on "Set as Target Platform". The rebuild will occur. You may see errors about org.eclipse.eavp, which may be ignored.
  5. Go to the "org.eclipse.ice.repository" project, right click on the the launch configuration (ice.*.launch) for your OS and select Run As -> Run Configuration (In the near future a multi-OS product definition will be made available as a launch tool.)
    1. In the Run Configuration window: make the following changes:
      1. For Windows, the Triquetrum bundles have already been added to the launch configuration.
      2. If you are using Linux or Mac, click on the Plug-ins tab and add the following plug-ins:
        1. org.eclipse.ice.triquetrum (1 plug-in)
        2. diva (1 plugin)
        3. All ptolemy bundles (8 plug-ins, see below)
          1. org.ptolemy.commons
          2. ptolemy.actor.lib
          3. ptolemy.actor.lib.gui
          4. ptolemy.core
          5. ptolemy.domains.process
          6. ptolemy.domains.sdf
          7. ptolemy.gui
          8. ptolemy.moml
        4. All triquetrum bundles (8 plug-ins, see below)
          1. org.eclipse.triquetrum.common
          2. org.eclipse.triquetrum.processing.api
          3. org.eclipse.triquetrum.processing.model.impl.memory
          4. org.eclipse.triquetrum.processing.services.impl
          5. org.eclipse.triquetrum.validation.api
          6. org.eclipse.triquetrum.workflow.actor.ui
          7. org.eclipse.triquetrum.workflow.api
          8. org.eclipse.triquetrum.workflow.execution.impl
          9. org.eclipse.triquetrum.workflow.model
          10. org.eclipse.triquetrum.workflow.ui
        5. Following bundles should be set with "Auto-Start=true" in your launch configuration :
          1. ptolemy.actor.lib
          2. ptolemy.domains.process
          3. ptolemy.domains.sdf
          4. ptolemy.moml
          5. org.eclipse.ice.triquetrum
          6. org.eclipse.triquetrum.workflow.actor.ui
            1. FIXME: The above is not present for Christopher
            2. RETEST: Should be fine after update of your Triq workspace with the missing bundles?
          7. org.eclipse.triquetrum.workflow.execution.impl
          8. org.eclipse.triquetrum.workflow.repository.impl.filesystem
            1. FIXME: The above is not present for Christopher
            2. RETEST: Should be fine after update of your Triq workspace with the missing bundles?
          9. org.eclipse.triquetrum.workflow.ui
        6. Click on Validate Plug-ins, which should report that there are no errors
        7. Click on the Run button. If a dialog appears that mentions errors in eavp, then click on Proceed.
  6. ICE will start up.
  7. Select a workspace
  8. Go to the ICE perspective and in the Item Viewer at the left create the Triquetrum Item by clicking on the green plus button. The Triquetrum Item is currently at the bottom of the list : TriquetrumWorkflowItemModel.
  9. You should get an ICE Item Form for trying Triquetrum workflows. For the moment this should show 2 dummy test flows called "hello" and "goodbye".
  10. Select one workflow and Save (Ctrl-S or similar depending on your OS). A minimal workflow configuration form should appear on the right in the Item form, with just one field. This is linked to a parameter in the test workflow model. You can specify a message in the field, that will be shown in a small Display shell when you run the workflow by clicking the Go! button.

When all goes well, you should get a result similar to :

Triquetrum in ICE screenshot.jpg

FIXME: The Display window does not appear for Christopher. The console in the ICE Eclipse says:

19:23:46.401 [pool-2-thread-1] INFO  o.e.t.w.e.i.e.WorkflowExecutionTask - Context d93598ca-684e-441a-b20f-184595778460 - Execution finished of model hello
Error opening window for Display actor.
ptolemy.kernel.util.IllegalActionException: Cannot find effigy for top level ".hello".  This can happen when a is invoked with a non-graphical execution engine such as ptolemy.moml.MoMLSimpleApplication but the  ptolemy.moml.filter.RemoveGraphicalClasses MoML filter is not replacing the class that extends Display.
	at ptolemy.actor.lib.gui.DisplayJavaSE$3.run(DisplayJavaSE.java:198)
	at ptolemy.gui.Top._executeDeferredActions(Top.java:1531)
	at ptolemy.gui.Top.access$9(Top.java:1515)
	at ptolemy.gui.Top$DeferredActionsRunnable.run(Top.java:2059)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
	at java.awt.EventQueue.access$500(EventQueue.java:97)
	at java.awt.EventQueue$3.run(EventQueue.java:709)
	at java.awt.EventQueue$3.run(EventQueue.java:703)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

RETEST: Should be fine after update of your Triq workspace with the missing bundles?

Back to the top