Skip to content
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

cartographer_node does not publish Poses #30

Open
rotu opened this issue Jun 21, 2019 · 3 comments
Open

cartographer_node does not publish Poses #30

rotu opened this issue Jun 21, 2019 · 3 comments

Comments

@rotu
Copy link

rotu commented Jun 21, 2019

The cartographer_node only publishes the location of the robot relative to the map as a Transform, and does not publish the robot position as geometry_msgs.msg.PoseWithCovariance. It would be nice to have it as a pose for purposes of navigation and/or sensor fusion.

@clalancette
Copy link

The cartographer_node only publishes the location of the robot relative to the map as a Transform, and does not publish the robot position as geometry_msgs.msg.PoseWithCovariance. It would be nice to have it as a pose for purposes of navigation and/or sensor fusion.

Seems reasonable. As far as I can tell, this is a decision that upstream cartographer_ros has made, so I'd suggest opening a PR there; we'll inherit it the next time we do an update.

@rotu
Copy link
Author

rotu commented Jun 21, 2019

There is no suitable upstream cartographer_ros branch using ROS2. Perhaps there should be?

@clalancette
Copy link

There is no suitable upstream cartographer_ros branch using ROS2. Perhaps there should be?

Yes, there should be. It essentially entails someone working with upstream cartographer_ros to propose a design document, respond to comments, and do the work to start feeding the port to whatever is decided there. Unfortunately, I do not have the time to do this work, but I would be happy to provide some side support and guidance for someone who wants to take this on.

In the meantime, another viable path would be to add the PoseWithCovariance publication you want to the upstream master (ROS 1) branch. It would then be a straightforward piece of the 'port' that we are maintaining here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants