-
Notifications
You must be signed in to change notification settings - Fork 672
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(crosswalk): fix passing direction calclation for the objects #9071
fix(crosswalk): fix passing direction calclation for the objects #9071
Conversation
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9071 +/- ##
==========================================
- Coverage 26.77% 26.76% -0.02%
==========================================
Files 1296 1301 +5
Lines 95822 95868 +46
Branches 39145 39146 +1
==========================================
+ Hits 25657 25658 +1
- Misses 67518 67563 +45
Partials 2647 2647
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
d01ae0d
into
autowarefoundation:main
…owarefoundation#9071) Signed-off-by: Yuki Takagi <yuki.takagi@tier4.jp> Signed-off-by: Kyoichi Sugahara <kyoichi.sugahara@tier4.jp>
Description
If the crosswalk width is narrow than sparse_resample_interval, which is had coded as 4.0m, passing direction calculation may failed because idx1 == idx2 is satisfied.
This PR fix this issue, and now both of the same directional objects and the opposite directional objects are ignored as a crosswalk user.
Related links
#5849
How was this PR tested?
scenario tests
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.