fix(path_generator): fix path bound for overlapped lanes #280
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In the previous calculations, toArcCoordinates in overlapping lanes would find s in the first lane.
Even if s is in return lane, the s for outward lane will be calculated.
In this PR,
calc_bound_s_range
is modified to find the lane containing s at the centerline and calculate s at the boundary of same lane.before

after
get_first_self_intersection_arc_length
not calculate the intersection before s_start.So far, the intersection before s_start was also calculated if it was in the current lane. This will delay the timing of path cut release.
prevent
hi < lo
when*s_intersection - vehicle_info_.max_longitudinal_offset_m
is negativeRelated links
tier4 internal slack
Parent Issue:
How was this PR tested?
path_cut-2025-03-16_21.19.06.mp4
path_cut-2025-03-16_21.17.10.mp4
2025/03/16 https://evaluation.tier4.jp/evaluation/reports/0452bf5a-59d4-5bbf-aed4-8764dba357d7/?project_id=prd_jt
2025/03/17 https://evaluation.tier4.jp/evaluation/reports/35423c04-0ab5-5771-b10d-4b9c7979100f/?project_id=prd_jt
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.