-
Notifications
You must be signed in to change notification settings - Fork 310
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
Make ROS2 OdometryServer composable #162
Comments
@roncapat Thanks for the suggestion. As I read this, I get to know about components in ROS 2. So, I'm literally blind to this topic. I'm more than willing to help review a merge request about this. Would you be interested in doing so? If not, could you provide some pointers on where to start and what example to look in order to achieve this? Thanks! |
Of course :) |
If you'd like to know more about composition, a paper has been released this week :) |
Just saw the post yesterday on LinkedIn. Amazing works from Steve as usual |
It shall be easy to transform OdometryServer in a ROS2 component. In this way, you could provide:
... at the same time.
Moreover, the component would benefit of much higher transfer rate of PointClouds messages thanks to intra-process communication.
Would you like a patch to provide this?
The text was updated successfully, but these errors were encountered: