You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: planning/behavior_path_dynamic_avoidance_module/README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -23,15 +23,15 @@ The inner algorithms can be separated into two parts: The first decide whether t
23
23
If you are interested in more details, please see the code itself.
24
24
25
25
### Select obstacles to avoid
26
-
To decide whether to avoid an object, both the predicted path and the state (poes and twist) of each object are used.
26
+
To decide whether to avoid an object, both the predicted path and the state (pose and twist) of each object are used.
27
27
The type of objects the user wants this module to avoid is also required.
28
28
Using this information, the module decides to *avoid* objects that *obstruct the ego's passage* and *can be avoided*.
29
29
30
30
The definition of *obstruct own passage* is implemented as the object that collides within seconds.
31
31
This process wastes computational cost by doing it for all objects; thus, filtering by the relative position and speed of the object with respect to the ego's path is also done as an auxiliary process.
32
32
The other, *can be avoided* denotes whether it can be avoided without risk to passengers or other vehicles.
33
33
For this purpose, it is judged whether the obstacle can be avoided by satisfying the constraints of lateral acceleration and lateral jerk.
34
-
For example, the modeule decides not to avoid an object that is too close or fast in the lateral direction because it cannot be avoided.
34
+
For example, the module decides not to avoid an object that is too close or fast in the lateral direction because it cannot be avoided.
35
35
36
36
### Cuts off the drivable area against the selected obstacles
37
37
For the selected obstacles to be avoided, the module cuts off the drivable area.
@@ -47,7 +47,7 @@ We can limit the lateral shift length by `drivable_area_generation.max_lat_offse
Then, extracting the same directional and opposite directional obstacles from the drivable area will work as follows considering TTC (time to collision).
52
52
53
53
Regarding the same directional obstacles, obstacles whose TTC is negative will be ignored (e.g. The obstacle is in front of the ego, and the obstacle's velocity is larger than the ego's velocity.).
@@ -61,7 +61,7 @@ Opposite directional obstacles (Parameter names may differ from implementation)
0 commit comments