-
Notifications
You must be signed in to change notification settings - Fork 704
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(start_planner): remove front of shift start pose from collision check section #6374
fix(start_planner): remove front of shift start pose from collision check section #6374
Conversation
Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #6374 +/- ##
==========================================
- Coverage 14.88% 14.88% -0.01%
==========================================
Files 1838 1838
Lines 126699 126709 +10
Branches 38042 38042
==========================================
Hits 18865 18865
- Misses 86535 86545 +10
Partials 21299 21299
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
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.
thanks! LGTM!
// remove the point behind of collision check end pose | ||
combined_path.points.erase( | ||
combined_path.points.begin() + collision_check_end_idx + 1, combined_path.points.end()); | ||
return combined_path; |
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.
memo:
this kept points before all points before collision_check_end_idx including points before start pose
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
…alization (autowarefoundation#6376) * separate debug and info marker Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> * replace util function for footprint Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> --------- Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
bfa18fa
to
d29cb27
Compare
confirmed no degression with start_planner related scenario. |
a10f9c4
into
autowarefoundation:main
…heck section (autowarefoundation#6374) * remove front of shift start pose Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> * Refactor collision check section extraction in StartPlannerModule Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> --------- Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
…heck section (autowarefoundation#6374) * remove front of shift start pose Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> * Refactor collision check section extraction in StartPlannerModule Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> --------- Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
…heck section (autowarefoundation#6374) * remove front of shift start pose Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> * Refactor collision check section extraction in StartPlannerModule Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp> --------- Signed-off-by: kyoichi-sugahara <kyoichi.sugahara@tier4.jp>
Description
points front of shift start pose was used for collision check

That was causing the problem of not generating shift pull out path when object is located at behind of ego vehicle
Now shift pull out path can be generated even when object is located at behind of ego vehicle

Tests performed
Effects on system behavior
Not applicable.
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.