-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(lane_change): guard invalid lc start point #3257
fix(lane_change): guard invalid lc start point #3257
Conversation
Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #3257 +/- ##
=======================================
Coverage 13.21% 13.22%
=======================================
Files 1263 1263
Lines 89337 89326 -11
Branches 27079 27081 +2
=======================================
Hits 11809 11809
+ Misses 65104 65093 -11
Partials 12424 12424
*This pull request uses carry forward flags. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* fix(lane_change): guard invalid lc start point Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com> * fix(lane_change): remove macro Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com> --------- Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Description
The lane change start pose must NOT be in front of the
target_lanelets.front()
, and this is check in here.autoware.universe/planning/behavior_path_planner/src/util/lane_change/util.cpp
Lines 350 to 352 in 90ed30d
On the other hand, this guard doesn't support new architecture that can run multiple modules simultaneously.
If the lane change module uses avoidance path as input path, the start pose is generated on that path. In this case, there is a possibility that the start pose is in front of the
target_lanelets.front()
even if the above condition is satisfied.So, I added another condition so that distance (orange line) between lc start pose and target lane's front pose does not have a positive value.
Related links
Tests performed
Notes for reviewers
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.