pcd_to_pointcloud: add latch param using transient_local QoS #459
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remco-r
force-pushed
the
feature/latch_pcd_to_pointcloud_ros2
branch
from
33337d4
to
c50ee46
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I missed this feature from ROS1. Implemented using transient_local QoS.
Tested in humble using:
ros2 run pcl_ros pcd_to_pointcloud --ros-args -p file_name:=<file_path> -p latch:=trueAfterwards a single pointcloud was received with
ros2 topic echoor inrviz, while these nodes were not active when the pointcloud was published.