-
Notifications
You must be signed in to change notification settings - Fork 244
Include option to use PointCloud Transport #761
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
Include option to use PointCloud Transport #761
Conversation
Signed-off-by: ElSayed ElSheikh <elsayed.elsheikh97@gmail.com>
SteveMacenski
left a comment
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.
LGTM! Can you add in the migration guide reference for support for point cloud transport compression in the collision monitor and costmap layers?
Sure! :-) |
|
@elsayedelsheikh I think that's all that's blocking here. I'd be curious if you had any perf metrics if using compression vs not using compression to share in it :-) |
Signed-off-by: ElSayed ElSheikh <elsayed.elsheikh97@gmail.com>
Signed-off-by: ElSayed ElSheikh <elsayed.elsheikh97@gmail.com>
|
@SteveMacenski Check this migration guide. The guide currently covers bandwidth only for performance metrics as I didn't mention encoding/decoding speed, lossy vs. lossless, or CPU load. I guess if the sensor manufacturer provides |
0ff80e9 to
cac522c
Compare
Updates related to ros-navigation/navigation2#5264