Difference between revisions of "MAPIR's Module Architecture"

From The BABEL Development Site
(New page: <center> <big>A proposed architecture framework for developing BABEL modules</big> </center> <hr> <b>Abstract.</b> <i>This report addresses the problem of designing low-level modules fo...)
 
Line 1: Line 1:
 
 
<center>
 
<center>
<big>A proposed architecture framework for developing BABEL modules</big>
+
<b><big>A proposed architecture framework for developing BABEL modules</big></b>
 
</center>
 
</center>
 
<hr>
 
<hr>

Revision as of 14:29, 17 May 2009

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