Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Papyrus/customizations/robotics/bt

< Papyrus‎ | customizations/robotics
Revision as of 09:26, 29 September 2020 by Unnamed Poltroon (Talk) (Created page with "= Task and skill concepts = The skill abstraction interfaces the task level and the level in which software components are executed (called the service level in the RobMoSys p...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Task and skill concepts

The skill abstraction interfaces the task level and the level in which software components are executed (called the service level in the RobMoSys parlance, see Separation of Levels and Concerns in RobMoSys).

Skills make the functionalities realized by components accessible to the task level, without binding the behavior models to concrete components. The system sequencer, which is in charge of executing the task description, demands to the components the execution of their skills by means of a well-defined configuration and coordination interface. This approach conforms to the RobMoSys Architectural Patterns for Task-Plot Coordination and for Component Coordination.

How to define a new skill

Papyrus-customizations-robotics-DefinitionOfSkillStatic.png

How to create a new task in form of a behavior tree

Papyrus-customizations-robotics-DefinitionOfBTStatic.png

Export the behavior tree in XML format

Papyrus-customizations-robotics-ExportBTStatic.png

Realization of skills by components

Back to the top