The CLARAty architecture for robotic autonomy
This paper presents an overview of a newly developed Coupled Layer Architecture for Robotic Autonomy (CLARAty), which is designed for improving the modularity of system software while more tightly coupling the interaction of autonomy and controls. First, we frame the problem by briefly reviewing pre...
Gespeichert in:
Hauptverfasser: | , , , , , |
---|---|
Format: | Tagungsbericht |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | This paper presents an overview of a newly developed Coupled Layer Architecture for Robotic Autonomy (CLARAty), which is designed for improving the modularity of system software while more tightly coupling the interaction of autonomy and controls. First, we frame the problem by briefly reviewing previous work in the field and describing the impediments and constraints that been encountered. Then we describe why a fresh approach to the topic is warranted, and introduce our new two-tiered design as an evolutionary modification of the conventional three-level robotics architecture. The new design features a tight coupling of the planner and executive in one Decision Layer, which interacts with a separate Functional Layer at all levels of system granularity. The Functional Layer is an object-oriented software hierarchy that provides basic capabilities of system operation, resource prediction, state estimation, and status reporting. The Decision Layer utilizes these capabilities of the Functional Layer to achieve goals by expanding, ordering, initiating and terminating activities. Both declarative and procedural planning methods are used in this process. Current efforts are targeted at implementing an initial version of this architecture on our research Mars rover platforms, Rocky 7 and 8. In addition, we are working with the NASA robotics and autonomy communities to expand the scope and participation in this architecture, moving toward a flight implementation in the 2007 time-frame. |
---|---|
ISSN: | 1095-323X |
DOI: | 10.1109/AERO.2001.931701 |