-
Notifications
You must be signed in to change notification settings - Fork 650
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(stop_line): z position of stop point #2239
fix(stop_line): z position of stop point #2239
Conversation
Signed-off-by: Tomohito Ando <tomohito.ando@tier4.jp>
Codecov ReportBase: 11.16% // Head: 11.15% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #2239 +/- ##
==========================================
- Coverage 11.16% 11.15% -0.01%
==========================================
Files 1200 1200
Lines 86184 86205 +21
Branches 20787 20805 +18
==========================================
Hits 9620 9620
- Misses 66439 66459 +20
- Partials 10125 10126 +1
*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 at Codecov. |
@takayuki5168 |
@@ -64,7 +64,6 @@ bool StopLineModule::modifyPathVelocity( | |||
|
|||
const auto stop_point_idx = stop_point->first; | |||
auto stop_pose = stop_point->second; | |||
stop_pose.position.z = (stop_line_[0].z() + stop_line_[1].z()) / 2.0; | |||
|
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.
When committing this line, I just followed the original implementation before my PR.
Currently, z position is interpolated from the path. So it makes sense to remove this line.
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
@purewater0901 |
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: z position of stop point Signed-off-by: Tomohito Ando <tomohito.ando@tier4.jp> Signed-off-by: Tomohito Ando <tomohito.ando@tier4.jp> Signed-off-by: Kotaro Yoshimoto <pythagora.yoshimoto@gmail.com>
fix: z position of stop point Signed-off-by: Tomohito Ando <tomohito.ando@tier4.jp> Signed-off-by: Tomohito Ando <tomohito.ando@tier4.jp> Signed-off-by: yoshiri <yoshiyoshidetteiu@gmail.com>
Signed-off-by: Tomohito Ando tomohito.ando@tier4.jp
Description
Currently z position of stop line is used as the z position of inserted point, but it causes z position error.
(e.g. when there is a stop line in a slope.)
That resulted in strange pitch due to the high elevation angle.
z position of stop point is calculated here, so I think this calculation is not needed.
before this change:
I visualized the output path poses from stop_line module.
after this change:
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.