Add a guide for creating new conversion packages for rosidl::Buffer#6654
Merged
Conversation
Signed-off-by: CY Chen <cyc@nvidia.com>
|
HTML artifacts: https://github.com/ros2/ros2_documentation/actions/runs/25677433100/artifacts/6921715528. To view the resulting site:
|
ahcorde
approved these changes
May 11, 2026
mjcarroll
approved these changes
May 11, 2026
ahcorde
pushed a commit
that referenced
this pull request
May 11, 2026
This file contains hidden or 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
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.
Description
Add a new page for a guide to creating a new conversion packages for
rosidl::Buffer.The page explains how conversions packages differ from
rosidl::BufferBackendplugins: backends handle storage and transport, while conversions packages adapt existing ROS messages withuint8[]payload fields, such as tensors, images, or point clouds, into library-specific native types.It also includes tensor-specific guidance for
tensor_msgs/msg/ExperimentalTensor, documentstorch_conversionsas the first reference implementation, and outlines how future packages such as ONNX, NumPy, or CuPy conversions can interoperate through the common tensor message while using CPU or supported non-CPU buffer backends underneath.Did you use Generative AI?
Yes, GPT-5.5 was used to help create an initial draft of the content.