Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 51fb124

Browse files
committedFeb 6, 2024·
update
Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
1 parent fe34b6b commit 51fb124

File tree

1 file changed

+0
-4
lines changed
  • planning/behavior_path_start_planner_module

1 file changed

+0
-4
lines changed
 

‎planning/behavior_path_start_planner_module/README.md

-4
Original file line numberDiff line numberDiff line change
@@ -89,10 +89,6 @@ The `StartPlannerModule` is designed to initiate its execution based on specific
8989

9090
5. **Goal behind in same route segment**: The module will not initiate if the goal position is behind the ego vehicle within the same route segment. This condition is checked to avoid complications with planning routes that require the vehicle to move backward on its current path, which is currently not supported.
9191

92-
These conditions are evaluated to ensure that the `StartPlannerModule` only initiates under safe and necessary circumstances, optimizing route planning efficiency and safety.
93-
94-
In summary, the `StartPlannerModule` will initiate if **none** of these conditions apply, ensuring that the module starts only when it is safe and necessary to do so.
95-
9692
### **End Conditions**
9793

9894
The `StartPlannerModule` terminates if the pull out / freespace maneuver has been completed. The `canTransitSuccessState` function assesses these conditions to decide if the module should terminate its execution.

0 commit comments

Comments
 (0)
Please sign in to comment.