ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
you are using AMCL and robot_pose_ekf at the same time they are trying solve the same problem. Using these same ekfs wont improve accurancy. use AMCL's filter and do the sensor fusion by raw data. it doesn't really make sense to use an already filtered pose as input.If you already have a map and would like to localize your robot in it, you should use amcl_pose.
2 | No.2 Revision |
you are using AMCL and robot_pose_ekf at the same time they are trying solve the same problem. Using these same ekfs wont improve accurancy. use AMCL's filter and do the sensor fusion by raw data. it doesn't really make sense to use an already filtered pose as input.If you already have a map and would like to localize your robot in it, you should use amcl_pose.amcl_pose. As for the /odom topic, it is subscribed by move_base not for the pose information but for the velocity
3 | No.3 Revision |
you are using AMCL and robot_pose_ekf at the same time they are trying solve the same problem. Using these same ekfs wont improve accurancy. use AMCL's filter and do the sensor fusion by raw data. it doesn't really make sense to use an already filtered pose as input.If you already have a map and would like to localize your robot in it, you should use amcl_pose. As for the /odom topic, it is subscribed by move_base not for the pose information but for the velocity
4 | No.4 Revision |
Using these same ekfs wont improve accurancy. use AMCL's filter and do the sensor fusion by raw data. it doesn't really make sense to use an already filtered pose as input.If you already have a map and would like to localize your robot in it, you should use amcl_pose. As for the /odom topic, it is subscribed by move_base not for the pose information but for the velocity