Results_Simulation
| Timestamp | Group | Comment |
|---|---|---|
| 0:00 | static | Start of the video. All drones are on the floor and working. |
| 0:01 | Requesting 6 active drones | |
| 0:04 | 6 drones (all except cyan and indigo) taking off | |
| 0:06 | Registering #1 (blue) as faulty |
|
#1 lands #7 (indigo) takes off to replace it |
||
| 0:08 | Registering #2 (red) as faulty |
|
#2 lands #8 (cyan) takes off to replace it |
||
| 0:17 | reparation | Registering #2 as repaired allocation doesn't change, but #2 will be ready for subsequent failures |
| 0:18 | dynamic | Starting planification Admiral and Captain nodes are unblocked |
| 0:19 | first admiral orders issued (green cylinders) Letters A-F show current active-connected allocation |
|
| 0:22 | first captain orders issued (yellow lines) colored dots show the next waypoint for drones to reach |
|
| 0:38 | Rviz refresh glitch : admiral orders are not updated | |
| 1:02 | Drone #5 (yellow) registered as faulty |
|
| 1:04 |
#5 starts landing sequence #2 (red) is taking off to replace it |
|
| Reallocation occurs: | ||
you can observe #6 (orange) replacing #5 as active drone C and moving to C target #7 becomes D instead of #6 and moves to D target.. and so on |
||
| 1:18 |
#2 is active - reallocation occurs |
|
| you can observe letters A-F mapped to the drones position captain orders show 6 paths to follow |
||
| 1:31 | shutdown | - system falls back to 2 active drones : #2, #3, #4, #6 enter landing sequence |
you can observe #2 getting back to the last reached waypoint as its mission got cancelled just before reaching the target |
||
| 1:35 | the 4 drones above have landed admiral orders have only 2 targets left | |
| 1:49 | system shuts down (0 active drones) #7 and #8 get their missions cancelled and enter landing sequence |
|
| 1:54 | all drones are landed - end of demonstration |