Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

ID

Acronym: Simulation Environment Monitoring

Use-cases: Loire Flooding, HelloDiag

Description

R-IOSEMIT enables you to simulate a predefined set of data called events. An event has to follow a predefined structure and a topic. In R-IOSuite three types of sensors can be simulated: the events emitted from webservices, from tweets or from the Maple location tags.



How does the interpretation work?

R-IOSEMIT enables R-IOSUITE to interpret events in real-time. It uses a Complex Event Processing (CEP) engine to apply the interpretation rules available in your Use-Case (at src/main/resources/webjars/gind/usecases/loireflooding/interpretation-rules.

R-IORED will be design to update these rules through a dedicated tool.

  • The first event is notified to the CEP engine by the notify() method of the CEP rules manager
  • The second event is notified to the CEP engine etc.
    ...
  • When an event fulfills the conditions of an interpretation rule, the High level interpretation engine notifies that a node or a edge has to be deleted/updated or added to the ACTIVE WORLD (stored in Neo4J). This action is stated in the interpretation rule.
  • Then, the interpretation manager uses the notification to update the ACTIVE WORLD with the interpret() method.



  • No labels