fix(autoware_ekf_localizer): publish processing time detail #9245
+14
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There are several tools for visualizing processing_time in
autoware_tools
.However,
autoware_ekf_localizer
currently does not publish the required topic. To use the above tools, a node needs to publish a topic with the typeautoware::universe_utils::ProcessingTimeDetail
(link1, link2).Therefore, this pull request adds a processing_time publisher to
autoware_ekf_localizer
How was this PR tested?
planning_simulator
with sample_maplogging_simulator
with sample_rosbaglogging_simulator
with awsim_gt_data(TIER IV INTERNAL)e2e_simulator
with AWSIM v1.3.0(1)
processing_time_visualizer
(2)
system_performance_plotter
ros2 bag record -o /path/to/result_rosbag --use-sim-time -e '.*processing_time.*'
and
The
result
directory is generated at current directory.Notes for reviewers
None.
Interface changes
Topic changes
Additions and removals
~/debug/processing_time_ms
tier4_debug_msgs::msg::ProcessingTimeTree
Under default settings, this is
/localization/pose_twist_fusion_filter/ekf_localizer/debug/processing_time_ms
.Effects on system behavior
None.