[Fix] Reduce the calculation load of points2image #1286
Merged
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.
Status
DEVELOPMENT
Description
Fixed /points2image and /calibration_publisher. autowarefoundation/autoware_ai#162
In order to reduce processing load, we changed the following two points.
(1) Improve the part calculated using OpenCV.
(2) We stopped wasteful memory allocation processing and optimized it.
Also, the /camera_info and /projection_matrix topics are useless because they are designed to keep publishing the same value. Changed calibration_publisher to publish in latch.
Todos
Steps to Test or Reproduce
Prepare a rosbag file containing / points_raw and / image_raw and a camera calibration file in advance.
After calibration publisher and points image are started up, compare the CPU load before and after change.
Before : 50% to 110% CPU(When HDL32e LiDAR is used)
After : 20% or less CPU(When HDL32e LiDAR is used)