Difference between revisions of "MAPIR's Module Architecture"
m (Protected "MAPIR's Module Architecture" [edit=autoconfirmed:move=autoconfirmed]) |
|||
| Line 1: | Line 1: | ||
| + | <table width="95%"><tr> | ||
| + | <td align="left"> </td> | ||
| + | <td align="right"> <small>Next: [[Architecture:Motivation | Motivation]]</small></td></tr> | ||
| + | </table> | ||
| + | |||
| + | |||
| + | |||
| + | <hr> | ||
<center> | <center> | ||
<b><big>A proposed architecture framework for developing BABEL modules</big></b> | <b><big>A proposed architecture framework for developing BABEL modules</big></b> | ||
Revision as of 14:57, 17 May 2009
| Next: Motivation |
A proposed architecture framework for developing BABEL modules
Abstract
This report addresses the problem of designing low-level modules for robotics control architectures under the BABEL development environment. These modules are typically developed by different researchers or students and their integration into any high-level architecture represents a big challenge due to the heterogeneity and the variety of involved tasks. This specification aims to normalize the structure of the low-level part of robotics control architectures, related with sensory and motor issues. Their interfaces are normalized in an effort to give a long-term stabilized repertory of modules, as well as leading to architectures largely independent of the particular robotic platform they are executed on. Architecture designers are free to specify the high-level modules (world modeling, task planning or motion planning) as desired and exploiting the robot-independent services offered by this low-level architecture.
Index
The index can be found in the left side-bar, under "modules architecture".
