System architecture » History » Version 18
Rafael Bailon-Ruiz, 2020-10-07 15:07
Remove technicalities
1 | 4 | Rafael Bailon-Ruiz | h1. System architecture |
---|---|---|---|
2 | 1 | Rafael Bailon-Ruiz | |
3 | 8 | Rafael Bailon-Ruiz | CAMS is a software framework for cloud exploration using fleets of UAVs. The system drives a *fleet of UAVs* inside *clouds* acoording to *user's plans* and *collects sensor data*. Afterwards the information is processed by *dedicated atmosphere analysis algorithms* to produce 4D *cloud maps* that are simultaneously *stored in a database* for future use and *shown to operator* through a *graphical user interface*. This graphical user interface also provides operators the means to *manage the fleet of UAVs* . |
4 | 1 | Rafael Bailon-Ruiz | |
5 | 12 | Rafael Bailon-Ruiz | !system_overview.png! |
6 | 1 | Rafael Bailon-Ruiz | |
7 | h2. Main features |
||
8 | |||
9 | 11 | Rafael Bailon-Ruiz | The goal of this system is to provide an easy to use [[Graphical User Interface]] to perform four main features: |
10 | 1 | Rafael Bailon-Ruiz | |
11 | * **Monitor data acquisition :** |
||
12 | 11 | Rafael Bailon-Ruiz | ** Predicted 4D cloud maps (3D + time). |
13 | 1 | Rafael Bailon-Ruiz | ** Various data profiles, including raw data display and vertical atmospheric profiles. |
14 | %{background:lightgreen}insert images here ?% |
||
15 | |||
16 | * **Monitor fleet status :** |
||
17 | ** Current UAV positions on map. |
||
18 | ** Status updates for each UAVs, including current task, (predicted path ?), flight time, battery voltage and many others. |
||
19 | ** Dedicated interface for telepilots as a tool to validate generated flight plans (for safety). |
||
20 | %{background:lightgreen}insert images here ?% |
||
21 | |||
22 | * **Generate flight plans :** |
||
23 | ** Depending on current fleet status and map of cloud, the user will be able to require a UAV to execute a specific flight pattern. The interface aims at providing a user-friendly interface to generate complex flight plans. |
||
24 | %{background:lightgreen}insert images here ?% |
||
25 | |||
26 | * **Simulation :** |
||
27 | ** Using the simulation capabilities of the Paparazzi framework and MesoNH atmospheric simulation data, the whole system is able to run entirely on simulation. See "here":https://redmine.laas.fr/projects/nephelae/wiki/Simulation for more details. |
||
28 | %{background:lightgreen}insert images here ?% |
||
29 | |||
30 | 9 | Rafael Bailon-Ruiz | h2. Modes of operation |
31 | 1 | Rafael Bailon-Ruiz | |
32 | 17 | Rafael Bailon-Ruiz | CAMS designed to work in several [[modes of operation]] fulfilling different user use cases: |
33 | 1 | Rafael Bailon-Ruiz | |
34 | 12 | Rafael Bailon-Ruiz | * Pure simulation |
35 | * Mixed-reality |
||
36 | 1 | Rafael Bailon-Ruiz | * Field deployment |
37 | 9 | Rafael Bailon-Ruiz | * Mission replay |
38 | |||
39 | 18 | Rafael Bailon-Ruiz | h2. Main components |
40 | 9 | Rafael Bailon-Ruiz | |
41 | 18 | Rafael Bailon-Ruiz | The software is made of several key sub-systems: |
42 | 9 | Rafael Bailon-Ruiz | |
43 | 18 | Rafael Bailon-Ruiz | * **Graphical user interface:** Web-based user interface for the operation of the fleet of UAVs and display of sensor data and cloud maps. |
44 | 9 | Rafael Bailon-Ruiz | |
45 | 18 | Rafael Bailon-Ruiz | * **Paparazzi interface:** The "paparazzi autopilot":http://paparazziuav.org is a _libre_ software and hardware platform for autonomous unmanned aerial vehicles encompassing the flight controller and the ground station. CAMS provides a software interface that takes care of the communication with UAVs and the ground station to receive sensor data and control the fleet. |
46 | 9 | Rafael Bailon-Ruiz | |
47 | 18 | Rafael Bailon-Ruiz | * **Mapping:** |
48 | 9 | Rafael Bailon-Ruiz | ** Full dense maps of clouds using sparse data generated by the UAVs, with the help of "Gaussian Process Regression":https://scikit-learn.org/stable/modules/gaussian_process.html (GPR). |
49 | ** Higher level functions to estimate some cloud parameters from a dense map (segmentation, area, border, etc...). |
||
50 | ** Single map interface, behind which can be a GPR predicted map, or a section of MesoNH data to be used as ground-truth in simulation. |
||
51 | |||
52 | 18 | Rafael Bailon-Ruiz | * **MesoNH interface:** Provides functions to read "MesoNH":http://mesonh.aero.obs-mip.fr/mesonh54 atmospheric simulation databases so they can be used to simulate realistic cloud environments for UAV flight and sensor data acquisition. Wind, pressure, liquid water content, and many other variables can be exploited as emulated sensor data. |
53 | 9 | Rafael Bailon-Ruiz | |
54 | 18 | Rafael Bailon-Ruiz | * **Data server:** Aggregates all data coming down from flying or simulated UAVs (or any other source) into a single server instance. Any module which needs data, like the mapping module or the GUI module must require data from the data server. |