PRE2017 3 Group 17: Difference between revisions
Jump to navigation
Jump to search
m (Trying html code for summation) |
m (Layout change) |
||
| Line 20: | Line 20: | ||
=== Assumptions === | === Assumptions === | ||
* No obstacles | |||
* Drones can be operated as intended, in clear weather | |||
* All drones are identical | |||
=== Users and what do they require? === | === Users and what do they require? === | ||
Law enforcement | * Law enforcement | ||
Infrared cameras / live image (or video) feed / Riot detection? | ** Infrared cameras / live image (or video) feed / Riot detection? | ||
Farmers | * Farmers | ||
Camera / “final” image overview (no live feed needed) | ** Camera / “final” image overview (no live feed needed) | ||
Staatsbosbeheer | * Staatsbosbeheer | ||
Camera / “final” image overview (no live feed needed) | ** Camera / “final” image overview (no live feed needed) | ||
Rijkswaterstaat (grachten in Amsterdam, etc.) | * Rijkswaterstaat (grachten in Amsterdam, etc.) | ||
Submarine drones | ** Submarine drones | ||
Detailed images for inspection of dunes | ** Detailed images for inspection of dunes | ||
Festival organisers | * Festival organisers | ||
Detection of the movement of masses/Riot detection? | ** Detection of the movement of masses/Riot detection? | ||
Archeologie | * Archeologie | ||
Sensors for depth searching | ** Sensors for depth searching | ||
=== Requirements === | === Requirements === | ||
Equipment failure can be dealt with | * Equipment failure can be dealt with | ||
Image stitching requirements | * Image stitching requirements | ||
=== Approach & Milestones === | === Approach & Milestones === | ||
Have concrete idea | # Have concrete idea | ||
Have a basic model (single drone) | # Have a basic model (single drone) | ||
Lane coverage | ** Lane coverage | ||
Have a basic model (multiple drone) | # Have a basic model (multiple drone) | ||
Lane coverage | ** Lane coverage | ||
Have reformation of drone organisation after a drone crashes | # Have reformation of drone organisation after a drone crashes | ||
Take height, clarity, and camera angle in consideration | # Take height, clarity, and camera angle in consideration | ||
(Some object have a higher priority to be scanned) | # (Some object have a higher priority to be scanned) | ||
=== Deliverables === | === Deliverables === | ||
Revision as of 16:13, 8 February 2018
| Members of group 17 | |
| Eric Arts | 1004076 |
| Menno Hofsté | 0996144 |
| René Nijhuis | 0912331 |
| Erik Takke | 1000575 |
| David Tuin | 1013331 |
Surveillance/Inspection drones
Project Details
Problem Statement
How to effectively survey a large area with multiple, cooperating drones
Objectives
Create a model for efficiently surveying areas using multiple, communicating drones
Assumptions
- No obstacles
- Drones can be operated as intended, in clear weather
- All drones are identical
Users and what do they require?
- Law enforcement
- Infrared cameras / live image (or video) feed / Riot detection?
- Farmers
- Camera / “final” image overview (no live feed needed)
- Staatsbosbeheer
- Camera / “final” image overview (no live feed needed)
- Rijkswaterstaat (grachten in Amsterdam, etc.)
- Submarine drones
- Detailed images for inspection of dunes
- Festival organisers
- Detection of the movement of masses/Riot detection?
- Archeologie
- Sensors for depth searching
Requirements
- Equipment failure can be dealt with
- Image stitching requirements
Approach & Milestones
- Have concrete idea
- Have a basic model (single drone)
- Lane coverage
- Have a basic model (multiple drone)
- Lane coverage
- Have reformation of drone organisation after a drone crashes
- Take height, clarity, and camera angle in consideration
- (Some object have a higher priority to be scanned)
Deliverables
An algorithm and computer model