-
Notifications
You must be signed in to change notification settings - Fork 658
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(ndt_scan_matcher): adding exe time to diagnostics for checking runtime_monitor #4916
Conversation
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 the PR!
localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml
Outdated
Show resolved
Hide resolved
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 except the following part, thanks 🙏
@yvzksgl Your suggestion of adding a condition to generate warnings is very good in itself. |
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 would like to avoid settings that affect the applications this warning is followed by.
localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml
Outdated
Show resolved
Hide resolved
I can create a PR for autoware_launch. Also if you want to discuss about exe_time warning value I can create discussion about it. However, I am okay with 100 and it makes sense to me as well. |
Please add the autoware_launch PR link in the description, and make sure that both are merged at the same time. |
Please fix the following
|
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 fixed them but github still says there are conflicts. A bug should be occured on github or something, i guess. Do you mind if I ask you to take a look? Thank you. |
@yvzksgl Sure, but it may take a while since I have other things to do unfortunately. |
@yvzksgl Please resolve conflicts. |
Co-authored-by: kminoda <[email protected]>
Co-authored-by: kminoda <[email protected]>
Co-authored-by: Motz <[email protected]>
Co-authored-by: Motz <[email protected]>
eeef736
to
cd5a8c8
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #4916 +/- ##
==========================================
- Coverage 14.89% 14.89% -0.01%
==========================================
Files 1625 1625
Lines 112449 112460 +11
Branches 34712 34712
==========================================
Hits 16752 16752
- Misses 76959 76970 +11
Partials 18738 18738
*This pull request uses carry forward flags. Click here to find out more.
☔ View full report in Codecov by Sentry. |
…untime_monitor (autowarefoundation#4916) * adding exe time to diagnostics * Update localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml Co-authored-by: kminoda <[email protected]> * order of the parameters in constructor corrected * spell check * Update localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp Co-authored-by: kminoda <[email protected]> * Update localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml Co-authored-by: Motz <[email protected]> * Update localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp Co-authored-by: Motz <[email protected]> * rebase branch to main * the actual execution time added to diagnostics message * execution_time parameter corrected * integration with header file * style(pre-commit): autofix * parameter naming --------- Co-authored-by: kminoda <[email protected]> Co-authored-by: Motz <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
…untime_monitor (autowarefoundation#4916) * adding exe time to diagnostics * Update localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml Co-authored-by: kminoda <[email protected]> * order of the parameters in constructor corrected * spell check * Update localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp Co-authored-by: kminoda <[email protected]> * Update localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml Co-authored-by: Motz <[email protected]> * Update localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp Co-authored-by: Motz <[email protected]> * rebase branch to main * the actual execution time added to diagnostics message * execution_time parameter corrected * integration with header file * style(pre-commit): autofix * parameter naming --------- Co-authored-by: kminoda <[email protected]> Co-authored-by: Motz <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
…untime_monitor (autowarefoundation#4916) * adding exe time to diagnostics * Update localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml Co-authored-by: kminoda <[email protected]> * order of the parameters in constructor corrected * spell check * Update localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp Co-authored-by: kminoda <[email protected]> * Update localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml Co-authored-by: Motz <[email protected]> * Update localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp Co-authored-by: Motz <[email protected]> * rebase branch to main * the actual execution time added to diagnostics message * execution_time parameter corrected * integration with header file * style(pre-commit): autofix * parameter naming --------- Co-authored-by: kminoda <[email protected]> Co-authored-by: Motz <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Description
This PR offersto add exe_time to diagnostics.
Exe time is useful for observe does NDT have problems while matching scans. I can say with my observations, if NDT exe_time is exceeded 24ms, it will be most likely started to cannot match scans properly. So while I'm checking runtime_monitor i would like to see NDT exe_time. Formerly this PR is a part of #4854.
Related: autowarefoundation/autoware_launch#559
Tests performed
All added options runned through logging simulator and test vehicle.
Effects on system behavior
It gives a facility for observing changes in nearest_voxel_transformation_likelihood and exe_time.
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 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.