Obstacle Avoidance
Obstacle Avoidance
Free Trajectories
100
90
80
70
60
50
y
40
30
20
10
–10
–10 –5 0 5 10 15 20 25
x
X2 p2
N
r2(t)
C
M
X1
r (t )
r1(t )
p1
location of the centre of the obstacle C, which is either to the left or the right
of this line. If the centre C is left to the line X1 –X2 , the intermediate pose
M is selected on the right-hand side of the obstacle region, and vice versa.
In the figure, the initial dotted path is r(t) and the modified solid line paths,
generated with the intermediate waypoint M, are r1 (t) and r2 (t). Hence the
multiple UAV path planning algorithm developed in Chapter 6 is modified
to give the following:
Restricted TARGET
Regions
BASE
35
30 TARGET
25
UAV2
20
Y
15
10
BASE
UAV1
5
5 10 15 20 25
X
35
30 TARGET
25
UAV1
20
Y
15
10 UAV2
BASE
5 10 15 20 25
X
35
30 TARGET
25
20
Y
15 UAV2
Intermediate way point
10
BASE
5 UAV1
5 10 15 20 25
X
200
180 4
2 3
160
4
140 1
3
2
120 1
4
100 3
y
1 2
4
80
60 2
1 3
40 4
20 2 3
1
0
0 20 40 60 80 100 120 140 160 180 200
x
Initial paths (same as final paths if no modification)
Final paths after modification
Paths generated through intermediate waypoints
Figure 4.29 Five UAVs each with four waypoints in cluttered space. Reprinted
with permission of Elsevier
poses. The filled ellipses are the obstacles. Flyable paths are then produced
between the poses to give the nominal paths (dashed in the figure). The
obstacle intersections are handled by generating intermediate waypoints
and/or poses as explained in section 4.3.2. The intersection of paths with the
no-fly zones are determined iteratively for the clothoid arc segments, while
the intersection of lines with ellipses can be detected by simple geometry.
An intermediate pose or waypoint is produced for each intersection within
the obstacle safety zone. Following this, the paths are re-planned to pass
through the new waypoints.
From the figure, it is also seen that, when a path intersects with a single
obstacle, re-planning of a new path is simple, as it only has to avoid a single
obstacle. However, re-planning is difficult when obstacles appear in clusters,
as in the case of the second and third UAVs. In the case of the second UAV,
and in between the third and fourth waypoints, there are three obstacles
110 Cooperative Path Planning of Unmanned Aerial Vehicles
in a cluster. The first re-planning of the initial path intersects the other
obstacle and hence requires further re-planning to avoid all of the obstacles.
A similar situation arises for the third UAV, where a cluster of two obsta-
cles appear together. Finally, the curvature of the first four paths, ordered
from the top, are increased to that of the reference path, which is the path
length of fifth UAV. This is similar to the path planning for a cluttered envi-
ronment for mapped obstacles detailed in section 4.2 using the differential
geometric approach.
45
Pf
40 Pf
35
30
25
Y
20
15
10
Ps Ps
5 UAV2
UAV1
0
0 5 10 15 20 25 30 35 40
X
45
40 Pf Pf
35
30
25
Y
20
15
10 Ps
Ps
5
UAV1 UAV2
0
0 5 10 15 20 25 30 35 40
X
45
Tangent Pf
40 Pf
Circle
35 Bezier
polygon
30
25
Obstacles
Y
20
15
10
Ps
5
Ps
UAV1 UAV2
0
0 5 10 15 20 25 30 35 40
X
45
Tangent Pf
Pf
40 Circle
35
Bezier
30 polygon
25
Obstacles
Y
20
15
10
Ps
5 Ps
UAV1 UAV2
0
0 5 10 15 20 25 30 35 40 45
X
1000
800
600
100
400
50
Z
200
0 Y
0 200 400 600 0
800 1000
X
is applied on this database, which connects each point in the database to its
natural neighbours, thus forming a connectivity graph of obstacles to their
immediate neighbours. The UAV has to fly across these connecting lines
between the obstacles. In order to make sure that the distances between the
obstacles are large enough for the UAV, any connecting lines between the
obstacles whose length is less than the safety radius of the UAV is deleted
from the connectivity graph. Figure 4.35 shows the 2D projection of the
triangulation of 10 obstacles (buildings). The figure shows the connectivity
between their neighbourhoods – for example, the obstacle no. 9 at the bottom
right corner is connected to its neighbours 1, 4 and 8, but not to any others.
This helps to decide whether the UAV can fly in-between the obstacles.
This is done by calculating the available distance between the obstacles,
considering the size (radius) of the buildings. The small open circles are the
centre points (nodes) of the lines through which the UAV can fly. The nodes
are waypoints for the UAVs. Route planning is done by finding the shortest
route through these nodes. The Dijkstra search algorithm (Dijkstra 1959) is
used to find the route.
The waypoints can be connected using either Dubins, clothoid, or PH
paths. Here a Dubins path is used to connect the nodes. The height of the
waypoints can be chosen depending on the possible climb rate of the UAV.
The simulations in Figures 4.34 and 4.36 use 30 obstacles. The grey lines
are the triangulation of obstacle positions, and the thin black lines are the
1000
800
600
Y
400
1000
200 800
600
400
0 200 X
0
1000
900
800
700
600
500
Y
400
300
200
100
0
0 200 400 600 800 1000
X
triangulation formed by the nodes including the start point (node no. 1) and
goal point (node no. 32). The numbers on the buildings are the label numbers
for each building.
References
Agarwal, P. K., Biedl, T., Lazard, S., Robbins, S., Suri, S. and Whitesides, S. 2002.
Curvature-constrained shortest paths in a convex polygon. SIAM Journal of Com-
puting, 31(6), 1814–1851.
Assaf, D. and Sharlin-Bilitzky, A. 1994. Dynamic search for a moving target. Journal
of Applied Probability, 31(2), 438–457.
Beard, R., McLain, T., Goodrich, M. and Anderson, E. 2002. Coordinated target
assignment and intercept for unmanned air vehicles. IEEE Transactions on Robotics
and Automation, 18(6), 911–922.
Benkoski, S. J., Monticino, M. G. and Weisinger, J. R. 1991. A survey of the search
theory literature. Naval Research Logistics, 38(4), 468–494.
Berg, M., Kreveld, M., Overmars, M. and Schwarzkopf, O. 2000. Computation Geometry,
Algorithms and Applications. Springer.
Bicchi, A. and Pallottino, L. 2000. An optimal cooperative conflict resolution for air
traffic management systems. IEEE Transactions on Intelligent Transportation Systems,
1(4), 221–232.