Page History

...

This sub project implements an interface of the KIELER project for the simulation and execution of graphical domain specific models (e.g., EMF models). It itself does not do any simulation computation but bridges simulation components, visualization components and a user interface within the KIELER Eclipse rich client platform. To get a first impression about this sub project please feel free to watch the following  Flash demo video.

...

JavaDoc

Find the official JavaDoc documantation of the KIELER Execution Manager.

...

Quick start

Install

Check out the KIEM Eclipse plug-in project and enable it in your run configuration. Make sure to enable all required projects and to include all DataComponents you wish to use e.g., for visualization or simulation (s.b.).

...

The KIELER Execution Manager offers a launch configuration extension, see KIEM - KIEM Launch Configurations.

...

How does it work?

Scheduling

...

If you want to contribute a simulation or execution engine or any visualization facility to the KIELER project, you just need to understand about the two Extension Points that are explained below:

• de.cau.cs.kieler.sim.kiem.json.datacomponent (handles JSONObjects)
• de.cau.cs.kieler.sim.kiem.string.datacomponent (handles JSONStrings)

Both Extension Points are based on the same (abstract) super-class which is called AbstractDataComponent (AbstractDataComponent.java) and itself implements an interface called IDataComponent (IDataComponent.java). A DataComponent may handle JSONObjects (using the following JSON implementation for java:  http://www.json.org/java/) directly or it may handle JSONStrings only. This is where the too two Extension Points differ and what is necessary to decide prior to the implementation of a concrete JSONObjectDataComponent or JSONStringDataComponent.

If you take a look at the class diagrams of the extension package, you will see that there are 5 methods that every DataComponent needs to supply:

...

The method step() is called during the execution. It depends on the interface that is implemented what kind of data is passed as a parameter (JSONString or JSONObject) and also what (same!) kind is expected to be returned by the implementation. The parameter of the step() method contains the requested data. It depends on the following:

The methods isProducer() and isObserver() must be implemented and should return a boolean value indicating whether the DataComponent wants to receive any data (s.a.) or produces data or even both. There is a possibility of so called Initialization DataComponents that neither receive nor produce any data but only are used during the initialization and wrap-up phase when their initialize() and wrapup() method is called.

Take in mind that if your DataComponent is not both, an observer and a producer of data, it's step() method will not be called in a blocking scheme during the scheduled execution (for details please see above). If this is required, then you need to set the according return values to both being true.

...

This should give an overview about the base packages of the KIEM project:

1. The kiem package contains the KiemPlugin activator, the basic interfaces for the extension points (API), the KiemEvents?, the KiemExceptions? and the externalized strings.
2. The ui.views package implements the tree table view and most of the gui part.
3. The ui package contains additional gui helpers like the text fields, icons and special SWT widgets.
4. The properties package contains some basic KiemPropertyTypes as well as an interface and abstract class to extend those.
5. The internal package accommodates some internal interfaces and abstract classes for the Extension Points. The AbstractDataComponent? class may be of most interest for deciding which methods to override.
6. The execution package implements the scheduling and threaded execution.

Please feel free to browse the source and the JavaDoc documantation for further more detailed information.

...

Download

• Source: KIEM
• Source: RawTable
• Source: ABRO in JAVA
• Source: Synchronous Signal Resetter

• Source: SimpleRailCtrl Editor
• Source: SimpleRailCtrl C-Code Generator
• Source: SimpleRailCtrl Ptolemy Simulator
• Source: SimpleRailCtrl View Management

...

Case Studies

ABRO in Java

This illustrates the famous ABRO example, the "hello world" of the synchronous world. It is simply a Java plug-in implementing an observing and producing DataComponent that reacts to signals A, B, R with producing a present signal O whenever signal A and B just became present (in any order or even at the same time). The SyncChart then goes into the done state and is reset by signal R, i.e. it becomes ready and again waits for signals A and B. The strong abortion of the reset transition indicates that whenever R is present, in the same tick no O will be produced.

...

As another case study there exists a SimpleRailControlEditor for the  model railway of the Christian-Albrechts University of Kiel. It lets you create controllers for the model railway by modeling them with a generated Eclipse GMF editor. These models can be transformed into executable C-Code by a model2text-Xpand-transformation on the one hand. On the other there exists a complete Xtend-transformation which generates executable and I/O-equivalent  Ptolemy models out of them. The SimpleRailCtrl Ptolemy Simulator DataComponent is then capable of executing these Ptolemy models using the  Triq Ptolemy Eclipse plug-in. Together with the KIELER model visualizer the active states (nodes) of the controller model can then be illustrated during the execution.

There also exists a  demo video that shows the just described behavior. Whenever the execution is being initialized the Ptolemy simulator will transform the currently saved EMF model of the opened diagram into a semantically equivalent but executable ptolemy moml-File.