| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Copied answer from https://github.com/introlab/rtabmap/i...:
rtabmap publishes both TF and the nav_msgs/Odometry topic like this ROS tutorial.
The advantage to use the topic is to get the covariance of the pose. You can also get the twist directly. The disadvantage is when you need to synchronize with other sensors, you may not get the correct transform if the odometry topic cannot be exactly synchronized with the other sensors.
When using odom from TF, you can invert the advantages and disadvantages of the topic above. If you don't care about the covariance, use TF to get accurate transforms for a sensor's timestamp.
Asked: 2020-04-23 21:54:15 -0500
Seen: 669 times
Last updated: Apr 26 '20
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.
Not exactly sure what use case you're working on, but if your robot has encoders and is publishing on an odom topic, rtabmap can use that to better localize itself. If your robot doesn't publish to /odom, or you don't have a robot at all, rtabmap it relies on keypoint detection for its dead reckonin.