Difference between revisions of "Multi-UAV system design"
From Self-Organization Wiki
| Line 1: | Line 1: | ||
| + | == Group 1 == | ||
| + | |||
| + | Roland Siegwart, Evsen Yanmaz, Torsten Andre, Christof Hoppe, Michael Rischmuller, István Fehérvári, Wilfried Elmenreich | ||
| + | |||
| + | ===What is a multi-UAV system?=== | ||
| + | * airborne | ||
| + | * two or more UAVs, possibly also heterogeneous | ||
| + | * have to share knowledge | ||
| + | * information exchange during operation | ||
| + | * indirect or direct communication | ||
| + | * don't have to share a common objective | ||
| + | * collaboration or coordination | ||
| + | |||
| + | ===What are the building blocks of an autonomous multi-UAV system?=== | ||
| + | * networking, some form of communication | ||
| + | * sensing system: cameras, ultra-sonic | ||
| + | * interaction with the environment | ||
| + | * sharing representation | ||
| + | * bottom-up/top-down | ||
| + | ** bottom up: team of individuals | ||
| + | ** top down: designed as a team | ||
| + | * fail-operational or fail-safe | ||
| + | * swarm of simple systems/swarm with a leader/swarm of highly intelligent systems | ||
| + | |||
| + | ===What are the design challenges?=== | ||
| + | * technical challenges, see before | ||
| + | * mission-specific or one system fits all? | ||
| + | * system integration | ||
| + | * legal issues, regulations | ||
| + | * responsibility | ||
| + | * privacy | ||
| + | * public perception, acceptance | ||
| + | |||
| + | ===Is autonomy desirable? When?=== | ||
| + | * yes, for a large number of UAVs | ||
| + | * for a large area, remote location | ||
| + | * if problem is well-defined and easy | ||
| + | * no, to avoid legal issues | ||
| + | * if problem is complex, not trackable | ||
| + | |||
| + | == Group 2 == | ||
| + | |||
| + | == Group 3 == | ||
| + | |||
| + | == Group 4 == | ||
| + | |||
| + | == Group 5 == | ||
| + | |||
[[Group2_GW1]] | [[Group2_GW1]] | ||
[[Group 3]] | [[Group 3]] | ||
Revision as of 13:48, 8 July 2013
Contents
Group 1
Roland Siegwart, Evsen Yanmaz, Torsten Andre, Christof Hoppe, Michael Rischmuller, István Fehérvári, Wilfried Elmenreich
What is a multi-UAV system?
- airborne
- two or more UAVs, possibly also heterogeneous
- have to share knowledge
- information exchange during operation
- indirect or direct communication
- don't have to share a common objective
- collaboration or coordination
What are the building blocks of an autonomous multi-UAV system?
- networking, some form of communication
- sensing system: cameras, ultra-sonic
- interaction with the environment
- sharing representation
- bottom-up/top-down
- bottom up: team of individuals
- top down: designed as a team
- fail-operational or fail-safe
- swarm of simple systems/swarm with a leader/swarm of highly intelligent systems
What are the design challenges?
- technical challenges, see before
- mission-specific or one system fits all?
- system integration
- legal issues, regulations
- responsibility
- privacy
- public perception, acceptance
Is autonomy desirable? When?
- yes, for a large number of UAVs
- for a large area, remote location
- if problem is well-defined and easy
- no, to avoid legal issues
- if problem is complex, not trackable
