| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hello,
We're just getting started using the AMCL package for this robot. We're publishing odometry as described here, and so far, so good. I'm confused about something though: in the code, we're broadcasting nav_msgs/Odometry messages without setting the covariances (i.e. they're all zeros).
My question: is this a problem?
Thanks in advance,
Rick
Looking at the AMCL wiki page, you´ll notice that AMCL only subscribes to tf and gets the odometry pose from there. This means that covariance information is not used for AMCL (simply because it is not available via tf). The (probabilistic) motion model used within AMCL is determined by the AMCL node parameters.
One could certainly argue that the "proper" way of doing things would be subscribing to odometry messages and using the covariance information provided within, but this would also make setting up a real system harder.
> AMCL only subscribes to tf. Ah, thanks I see that now. Looks like I asked the wrong question. It's local_planner that makes use of odometry directly.
Hi! AMCL subscribes to tf but we still have to set a odom_frame_id... Why? Is it possible, and does it make sense, to use hector_mapping to compute odometry AND AMCL to compute the pose? Therefore, there would be 2 different map topics, one for AMCL (known map) one for hector_mapping.
Thanks!!
Asked: 2014-04-23 20:33:08 -0600
Seen: 869 times
Last updated: Apr 23 '14
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
