Closed kimjeff-korea closed 11 months ago
Do you have anything you can offer me? Parameters, terminal output, video, rosbag, etc.
I am testing the algorithm with original parameters except the set_initial_pose parameter.
When the initial_pose is set, the current_pose get transformed as expected but 2 meters shifted is the problem.
[INFO] [1686612220.182158226] [graph_based_slam]: initialize Publishers and Subscribers [INFO] [1686612220.182683501] [graph_based_slam]: initialization end [INFO] [1686612222.132553256] [scan_matcher]: create a first map [INFO] [1686612223.248649765] [scan_matcher]: initial_pose is received [INFO] [1686612237.260371774] [scan_matcher]: publish a map number of map points: 109938 [INFO] [1686612257.606718771] [scan_matcher]: publish a map number of map points: 226481
Here are a few images on Rviz.
left upper side axis is the published initial pose, left bottom axis is the reference odom axis, and the right axis is the current pose from lidar_slam.
I was wondering if someone had same issue. I might have missed something.
Found the solution for the issue. Creating a first map before the initial_pose received occurs the shift error.
Making sure let the slam node gets initial_pose before creating first map.
[INFO] [1686619327.049276943] [graph_based_slam]: initialize Publishers and Subscribers [INFO] [1686619327.049737715] [graph_based_slam]: initialization end [INFO] [1686619334.122100180] [scan_matcher]: initial_pose is received [INFO] [1686619335.526126605] [scan_matcher]: create a first map [INFO] [1686619353.498211912] [scan_matcher]: publish a map
Does anyone have the same problem when initial pose is set on the right position but the current pose start at the other place.