-
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
feat(pose_initializer, ndt_scan_matcher): check initial pose result and publish diag #8275
feat(pose_initializer, ndt_scan_matcher): check initial pose result and publish diag #8275
Conversation
Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp>
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp>
Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp>
Signed-off-by: RyuYamamoto <ryu.yamamoto@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.
I think, since there is no change about yabloc's initializer service, reliable
will be always false when using yabloc. Is it correct?
If so, in my opinion
(1) Best: judge by yabloc's score (If there is such a thing)
(2) Better: always returns true
I think that's right, for now, I will fix to always returns true. if implemented reliability judge logic in yabloc in the future, and I want to use it for judge reliability. |
Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8275 +/- ##
==========================================
+ Coverage 23.77% 29.23% +5.46%
==========================================
Files 1379 1603 +224
Lines 101362 116818 +15456
Branches 38527 50285 +11758
==========================================
+ Hits 24101 34157 +10056
+ Misses 74818 73475 -1343
- Partials 2443 9186 +6743
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Looks Good To Me
@@ -199,6 +199,8 @@ void CameraPoseInitializer::on_service( | |||
// Estimate orientation | |||
const double initial_yaw_angle_rad = 2 * std::atan2(orientation.z, orientation.w); | |||
const auto yaw_angle_rad_opt = estimate_pose(pos_vec3f, initial_yaw_angle_rad, yaw_std_rad); | |||
// TODO(localization/mapping team): judge reliability of estimate 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.
Thank you for adding TODO comment 👍
2c19f1e
into
autowarefoundation:main
…nd publish diag (autowarefoundation#8275) * feat(localization): check initial pose result and publish diag Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp> * fix: refactor Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp> * feat: update README Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp> * fix: rename reliability to reliable Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp> * feat: always return true in yabloc module Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp> --------- Signed-off-by: RyuYamamoto <ryu.yamamoto@tier4.jp> Signed-off-by: xtk8532704 <1041084556@qq.com>
Description
/diagnostics
topic.Related links
depend tier4/tier4_autoware_msgs#143
Parent Issue:
How was this PR tested?
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.