Versions Compared

Old Version 2

changes.mady.by.user Bartosz Palak

Saved on

compared with

New Version 3

changes.mady.by.user Bartosz Palak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For user conveniency it provides two kinds of interfaces: user friendly graphical interface that allows non-experienced users to define an actor in intuitive way and command line interface foreseen for more advanced users that may want to e.g. automatise actor generation process using scripts.


Info

Glossary

Scenario (aka workflow)

  • A set of components (actors) constituting a directed graph to execute a computing algorithm
  • Actors are dependent: a control and data is passed from actor to actor
  • Usually the order of actors execution and the way how data are passed from actor to actor is managed by so called "workflow system". Such manager can be a simple script (codes) or more sophisticated "orchestrator" (e.g. Kepler)

Actor

  • A basic component of scenario / workflow
  • An actor performs some actions (e.g. computations, visualisation, etc)
  • Usually given actor consumes results provided by a previous actor in a scenario and produces data for a next actor in a scenario

  • Actor API strictly depends on targeted workflow system: an orchestrator "fires" particular actions on actor 

  • An actor, using its internal mechanisms ('wrappers') calls 'native code' method(s), usually written in other language than an actor  

Native code

  • A physics code, of standardised signature, provided by software developer 

...

A signature of user code must follow strict rules to allow interaction between it and wrapping actor.  Please use following >>link<< to following  >>link<< to get detailed guidelines for integration of native code into workflows using iWrap  

...