Skip to content

Commit fbf6f66

Browse files
explanation for the valid paths
Signed-off-by: Muhammad Zulfaqar Azmi <zulfaqar.azmi@tier4.jp>
1 parent 4f999ec commit fbf6f66

File tree

1 file changed

+10
-8
lines changed
  • planning/behavior_path_lane_change_module

1 file changed

+10
-8
lines changed

planning/behavior_path_lane_change_module/README.md

+10-8
Original file line numberDiff line numberDiff line change
@@ -172,14 +172,16 @@ lateral_acceleration_resolution = (maximum_lateral_acceleration - minimum_latera
172172

173173
#### Candidate Path's validity check
174174

175-
A candidate path is valid if the total lane change distance is less than
176-
177-
1. distance to the end of current lane
178-
2. distance to the next intersection
179-
3. distance from current pose to the goal.
180-
4. distance to the crosswalk.
181-
182-
The goal must also be in the list of the preferred lane.
175+
A candidate path is considered valid if it meets the following criteria:
176+
177+
1. The distance from the ego vehicle's current position to the end of the current lanes is sufficient to perform a single lane change.
178+
2. The distance from the ego vehicle's current position to the goal, if within the current lanes, allows for multiple lane changes.
179+
3. The distance from the ego vehicle's current position to the end of the target lanes is adequate for executing multiple lane changes, regardless of whether the goal is within the current lanes.
180+
4. Intersection requirements are met (conditions are parameterized).
181+
5. Crosswalk requirements are satisfied (conditions are parameterized).
182+
6. Traffic light regulations are adhered to (conditions are parameterized).
183+
7. The lane change can be completed after passing a parked vehicle.
184+
8. The lane change is deemed safe to execute.
183185

184186
The following flow chart illustrates the validity check.
185187

0 commit comments

Comments
 (0)