Closed Kazunori-Nakajima closed 4 days ago
Thank you for contributing to the Autoware project!
🚧 If your pull request is in progress, switch it to draft mode.
Please ensure:
I would like to have the processing time output even in the case of an exception. We have moved the process of pubbing processing_time to handle_exception in service_utils. This allows us to output processing time even in the case of an exception.
- Codes are confusing and dirty.
- In case of error, it is not necessary to have it.
Because of the above two points, the processing time is not output in case of errors.
I'm committing various things, but I'm trying to output processing time both in error and in normal operation.
Attention: Patch coverage is 0%
with 14 lines
in your changes missing coverage. Please review.
Project coverage is 29.04%. Comparing base (
badf8ca
) to head (b1f9b32
). Report is 2 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🚨 Try these New Features:
Description
The processing time of
mission_planner
androute_selector
ware measured and made to Pub.Sometimes the processing time is pubbed twice during route generation. This is once for on_clear_route() and once for route on_set_lanelet_route().
(TIER IV internal usecase) This output is then read by the Basic scenario and tested daily for cycle failures.
Related links
How was this PR tested?
ros2 topic echo /planning/mission_planning/mission_planner/debug/processing_time_ms
ros2 topic echo /planning/mission_planning/route_selector/debug/processing_time_ms
https://github.com/user-attachments/assets/821baeb7-799f-47a3-a8ce-cfeb7fe0fdf4
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.