Aerospace and Electronic Systems - March 2019 - 42

ARIES: An Autonomous Controller For Multirobot Cooperation
a multiple robot team cooperates to perform missions
based on independent tasks. Each robot can sense with
some probability the effect of their own actions and the
actions of other team members through perception and
explicit broadcast communications. Then, each robot
selects its own tasks, considering that those tasks are
aligned for the benefit of the whole team. ALLIANCE
allows the robotic team to be fault tolerant, reliable, and
adaptable through the use of motivational behaviors.
These behaviors are designed to allow robot team members to perform tasks only as long as the task demonstrated a significant advance toward the team goal. Our
approach does not implement motivational behaviors,
instead we model simple behaviors to design our own
policies that aim to prevent robot failures from current
states, i.e., a leader failure does not have to trigger a follower failure or vice versa. As well, we model a fault tolerance domain on each robotic agent to prevent the
propagation of failure states. Other example is the Mission Oriented Operating Suite (MOOS) architecture [10],
which describes a behavior based and distributed controller to coordinate multiple AUVs for oceanic exploration
by using interval programming and solving multiobjective optimizations problems where the objective is
to minimize the path cost of each AUV. Our approach
follows a similar module-based philosophy to provide
scalability and flexibility for further developments, but it
does not implement interval programming neither multiobjective optimization for the path planning.
Other architectures distribute the mission goals of the
multiple robot team to follow a coordinated and robust execution flow. For instance, we can mention the M+ architecture [11], which distributes the mission goals in a
hierarchical manner where the low-level goals are locally
managed by each robot and high-level goals are managed
by a central node. M+ represents an extension of the LAAS
architecture [2] for a multiple robot frame. Our approach
follows a similar hierarchical approach (leader-follower
paradigm) where the deliberation process is centralized in
the leader, i.e., the leader is responsible for the planning of
cooperative high-level goals. As in M+, the low-level goals
aim to solve opportunistic robot failures. An architecture
that follows a similar approach is the High-level Distributed DecisioN (HiDDeN) [12], which is a distributed deliberative architecture that manages the execution of a
hierarchical plan for a multiple robot team in a specific air-
sea scenario. The hierarchical plan is distributed for its execution among the supervisor of the robots. Each robot has
its own supervisor, which contains the robots actions and
synchronization tasks with the others. Besides, the supervisors include a hierarchical repair process to provide fault
tolerance to the system. Both hierarchical plan and repair
processes are instantiated as hierarchical task networks
(HTN) [13], a common planning approach in cooperative
architectures. Our approach does not implement HTN for
42

the goals distribution. Our approach uses the planning
domain definition language (PDDL) [14] to model the
behavior of the multiple robot team following a coordination among their actions.
In practice, many architectures do not conform to a
strict paradigm dichotomy, e.g., many behavior-based
architectures employs hierarchical distribution of goals
and vice versa. In this way, many architectures has been
designed as hybrid systems which integrate several features in order to overcome complex problems. As a hybrid
paradigm, we want to highlight the leader-follower
approach, which has been extensively studied in the literature. The work of Chaimowicz et al. [15] proposes a
tightly coupled architecture where the communication
protocols allow the roles distribution and the coordination
among the robots. Also, it provides a mechanism for
dynamical distribution of roles. Parker et al. [16]
presented a cooperative architecture for the navigation
assistance task. Here, the leaders are sensor-rich robots
modeled to assist in the navigation of sensor-limited
robots (followers) which do not have on-board capabilities
for obstacle avoidance or localization. Our architecture
uses the hybrid leader-follower paradigm to share functionalities among the robotic systems in order to perform
complex missions. It does not provide dynamic roles
assignment but it can be easily adapted to any robotic system. CoT-ReX [17] is a hybrid architecture adapted to the
problem of underwater detection and localization. It uses
AUVs to gather information about the targets locations
while the Autonomous Surface Vehicle (ASV) acts as a
communication hub among all the AUVs. CoT-ReX has
been built under the T-REX system for the planning and
execution control of the mission. Nevertheless, CoT-ReX
keeps a centralized approach by executing a single T-REX
agent for the whole architecture, while our approach goes
further by providing a distributed execution in which each
robotic system executes its own T-REX agent.

A T-REX OVERVIEW
The purpose of this section is to introduce the T-REX
architecture [18], [19] to the reader. T-REX is a goaloriented system that follows the timeline-based planning
paradigm [20]-[22]. As Mayer et al. [23] describe, the
timeline-based planning paradigm aims to control complex physical systems through the synthesis of desired
temporal behaviors (called timelines) over robotic features
with associated temporal functions. In timeline-based
planning, these time-varying robotic features are called
state variables, e.g., the navigation system. Also, the values that a state variable can take over time are called as
tokens. Then, a timeline referred to a state variable is a
sequence of tokens that defines its temporal evolution,
such as the navigation control of a rover reporting its

IEEE A&E SYSTEMS MAGAZINE

MARCH 2019



Aerospace and Electronic Systems - March 2019

Table of Contents for the Digital Edition of Aerospace and Electronic Systems - March 2019

Contents
Aerospace and Electronic Systems - March 2019 - Cover1
Aerospace and Electronic Systems - March 2019 - Cover2
Aerospace and Electronic Systems - March 2019 - Contents
Aerospace and Electronic Systems - March 2019 - 2
Aerospace and Electronic Systems - March 2019 - 3
Aerospace and Electronic Systems - March 2019 - 4
Aerospace and Electronic Systems - March 2019 - 5
Aerospace and Electronic Systems - March 2019 - 6
Aerospace and Electronic Systems - March 2019 - 7
Aerospace and Electronic Systems - March 2019 - 8
Aerospace and Electronic Systems - March 2019 - 9
Aerospace and Electronic Systems - March 2019 - 10
Aerospace and Electronic Systems - March 2019 - 11
Aerospace and Electronic Systems - March 2019 - 12
Aerospace and Electronic Systems - March 2019 - 13
Aerospace and Electronic Systems - March 2019 - 14
Aerospace and Electronic Systems - March 2019 - 15
Aerospace and Electronic Systems - March 2019 - 16
Aerospace and Electronic Systems - March 2019 - 17
Aerospace and Electronic Systems - March 2019 - 18
Aerospace and Electronic Systems - March 2019 - 19
Aerospace and Electronic Systems - March 2019 - 20
Aerospace and Electronic Systems - March 2019 - 21
Aerospace and Electronic Systems - March 2019 - 22
Aerospace and Electronic Systems - March 2019 - 23
Aerospace and Electronic Systems - March 2019 - 24
Aerospace and Electronic Systems - March 2019 - 25
Aerospace and Electronic Systems - March 2019 - 26
Aerospace and Electronic Systems - March 2019 - 27
Aerospace and Electronic Systems - March 2019 - 28
Aerospace and Electronic Systems - March 2019 - 29
Aerospace and Electronic Systems - March 2019 - 30
Aerospace and Electronic Systems - March 2019 - 31
Aerospace and Electronic Systems - March 2019 - 32
Aerospace and Electronic Systems - March 2019 - 33
Aerospace and Electronic Systems - March 2019 - 34
Aerospace and Electronic Systems - March 2019 - 35
Aerospace and Electronic Systems - March 2019 - 36
Aerospace and Electronic Systems - March 2019 - 37
Aerospace and Electronic Systems - March 2019 - 38
Aerospace and Electronic Systems - March 2019 - 39
Aerospace and Electronic Systems - March 2019 - 40
Aerospace and Electronic Systems - March 2019 - 41
Aerospace and Electronic Systems - March 2019 - 42
Aerospace and Electronic Systems - March 2019 - 43
Aerospace and Electronic Systems - March 2019 - 44
Aerospace and Electronic Systems - March 2019 - 45
Aerospace and Electronic Systems - March 2019 - 46
Aerospace and Electronic Systems - March 2019 - 47
Aerospace and Electronic Systems - March 2019 - 48
Aerospace and Electronic Systems - March 2019 - 49
Aerospace and Electronic Systems - March 2019 - 50
Aerospace and Electronic Systems - March 2019 - 51
Aerospace and Electronic Systems - March 2019 - 52
Aerospace and Electronic Systems - March 2019 - 53
Aerospace and Electronic Systems - March 2019 - 54
Aerospace and Electronic Systems - March 2019 - 55
Aerospace and Electronic Systems - March 2019 - 56
Aerospace and Electronic Systems - March 2019 - 57
Aerospace and Electronic Systems - March 2019 - 58
Aerospace and Electronic Systems - March 2019 - 59
Aerospace and Electronic Systems - March 2019 - 60
Aerospace and Electronic Systems - March 2019 - 61
Aerospace and Electronic Systems - March 2019 - 62
Aerospace and Electronic Systems - March 2019 - 63
Aerospace and Electronic Systems - March 2019 - 64
Aerospace and Electronic Systems - March 2019 - 65
Aerospace and Electronic Systems - March 2019 - 66
Aerospace and Electronic Systems - March 2019 - 67
Aerospace and Electronic Systems - March 2019 - 68
Aerospace and Electronic Systems - March 2019 - Cover3
Aerospace and Electronic Systems - March 2019 - Cover4
https://www.nxtbook.com/nxtbooks/ieee/aerospace_december2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_november2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_september2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_august2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_july2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_june2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_may2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_april2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_march2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_february2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_january2023
https://www.nxtbook.com/nxtbooks/ieee/aerospace_december2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_november2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_september2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_august2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_july2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_june2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_may2022_tutorial
https://www.nxtbook.com/nxtbooks/ieee/aerospace_may2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_april2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_march2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_february2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_january2022
https://www.nxtbook.com/nxtbooks/ieee/aerospace_december2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_november2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_september2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_august2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_july2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_june2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_may2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_april2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_march2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_march2021_tutorials
https://www.nxtbook.com/nxtbooks/ieee/aerospace_february2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_january2021
https://www.nxtbook.com/nxtbooks/ieee/aerospace_november2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_december2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_september2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_august2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_july2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_june2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_may2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_april2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_march2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_february2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_january2020
https://www.nxtbook.com/nxtbooks/ieee/aerospace_december2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2019partII
https://www.nxtbook.com/nxtbooks/ieee/aerospace_november2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_july2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_september2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_august2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_june2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_april2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_may2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_march2019
https://www.nxtbook.com/nxtbooks/ieee/aerospace_december2018
https://www.nxtbook.com/nxtbooks/ieee/aerospace_august2018
https://www.nxtbook.com/nxtbooks/ieee/aerospace_october2018
https://www.nxtbook.com/nxtbooks/ieee/aerospace_september2018
https://www.nxtbook.com/nxtbooks/ieee/aerospace_november2018
https://www.nxtbookmedia.com