-
Notifications
You must be signed in to change notification settings - Fork 531
Extract extra fields from ROS2 PointCloud2
messages
#11193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Web viewer built successfully.
Note: This comment is updated whenever you push a commit. |
3906144
to
039b4f4
Compare
PointCloud2
messages for Points3D
PointCloud2
messages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome!
crates/utils/re_mcap/src/parsers/ros2msg/sensor_msgs/point_cloud_2.rs
Outdated
Show resolved
Hide resolved
crates/utils/re_mcap/src/parsers/ros2msg/sensor_msgs/point_cloud_2.rs
Outdated
Show resolved
Hide resolved
crates/utils/re_mcap/src/parsers/ros2msg/sensor_msgs/point_cloud_2.rs
Outdated
Show resolved
Hide resolved
Thank you @oxkitsune and @emilk for the feedback. I've addressed your comments if you want to take another look. |
match value { | ||
// Not part of the MCAP spec | ||
// // https://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/PointField.html | ||
PointFieldDatatype::Unknown => unreachable!(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still sounds like you can create an MCAP file (that is not spec compliant) that can crash the Rerun viewer.
For instance: a new MCAP spec is released with a PointFieldDatatype::Int128
, and the old parser will map that to Unknown
and Rerun crashes. NOT GOOD.
Instead: return an error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The loader runs in a separate thread that is specific to that MCAP file.
But overall I agree, we can't know in which context the loader will be running. I will add the error mechanism.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The loader runs in a separate thread that is specific to that MCAP file
We compile with panic=abort
, so a panic on any thread shuts down the whole process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL! I've made the required changes PR.
76ec0e0
to
7e4d534
Compare
almost working more cleanup merge race and lint
…ud_2.rs Co-authored-by: Gijs de Jong <14833076+oxkitsune@users.noreply.github.com>
7e4d534
to
ee40d84
Compare
What
This extracts additional values that are associated with points in the
PointCloud2
ROS2 messages. The fields will be added to thePoints3d
archetype as partially tagged.Screenshot
Test
We can use
autoware_all_sensors.mcap
to test.