The RobMoSys Wiki provides technical details on the RobMoSys approach including examples realizing the RobMoSys structures. The main philosophy behind the RobMoSys Wiki is to favour early access, openness, and transparency over completeness. This is to support communication of RobMoSys being a community endeavour. For general information about the RobMoSys project or its open calls, please refer to the project website.
RobMoSys enables the composition of robotics applications with managed, assured, and maintained system-level properties via model-driven techniques. It establishes structures that enable the management of the interfaces between different robotics-related domains, different roles in the ecosystem, and different levels of abstractions. Documents that provide an overview and introduction:
Please note: The RobMoSys consortium is continuously updating this wiki to provide early insights. See the Changelog. If you came here through a RobMoSys document, please see the RobMoSys Document Jumppage to find referred pages. This is a live and evolving wiki, stable Snapshots are available.
We provide a entry point and reading guide of the technical material for the RobMoSys Second Open Call which is open from February 2019 till end of April 2019. For information about the open call, refer to https://robmosys.eu/open-call-2/.
The RobMoSys Glossary contains descriptions of used terms. The technical FAQ provides answers to frequently asked questions.
Start reading here to see what your role is in the RobMoSys ecosystem or learn more about Roles in the Ecosystem. Main ecosystem users are:
Besides the ecosystem participants, there are also other roles like the Model-Driven Engineering tool developers (see RobMoSys Composition Structures) and framework builders (see Software Baseline). Read a quick introduction to the role of open call applicants in the project-level FAQ.
RobMoSys manages the interfaces between different roles and separates concerns in an efficient and systematic way by making the step change to a set of fully model-driven methods and tools for composition-oriented engineering of robotics systems. The following list of pages provide some fundamental principles in RobMoSys.
RobMoSys considers Model-Driven Engineering (MDE) as the main technology to realize the so far independent RobMoSys structures and to implement model-driven tooling. The wiki pages below collect some basic modeling principles related to realizing the RobMoSys structures.
RobMoSys allows the definition of domain-specific models and structures at composition Tier 2. To illustrate this concept, RobMoSys defines the following extendable content for Tier 2.
RobMoSys provides a set of tools and a software baseline that conform to the RobMoSys approach. This set can serve as a starting-point for applying the RobMoSys methodology or to extend it.
RobMoSys adopts a composition-oriented approach to system integration that manages, maintains and assures system-level properties, while preserving modularity and independence of existing robotics platforms and code bases, yet can build on top of them.
RobMoSys uses pilots to demonstrate the use of its approach through the development of full applications with robots. Pilots span different domains and different kind of applications. The pilots can be provided to project contributors to support designing, developing, testing, benchmarking and demonstrating their contribution.
The project is open for constructive suggestions from the community for further pilots or extensions to existing pilots, as long as “platform”, “composability” and “model-tool-code” are first-class citizens of those suggestions.
RobMoSys follows a reuse-oriented approach. This means that reinvention should be kept to a minimum and existing approaches should be used wherever possible. The following list provides some common approaches that are considered relevant within the RobMoSys context.
In this section, we feature early adoptors of RobMoSys methodology, composition structures, or tooling; we present community-related information.