| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hello, ROS people.
I am using ROS laser_scan_matcher but faced this ICP failure.
Please have a look the following video.
Is there anyone who encountered this and any recommendations?
Cheers.
(Warning: Shameless plug ahead) Not sure about ICP, but you could also try hector_mapping and see if it works better. We normally get good results with the Hokuyo UTM-30LX scanner and similar scenarios like that shown in your video.
/edit: Updated results with hector_mapping. I found that increasing the scan queue size from 5 to 25 gets rid of all errors, resulting in nice map without inconsistencies. It's a interesting question why that is though, considering that it takes only 4-8% of CPU (probably idling waiting for transforms). Map looks like this:
The results can be reproduced using this launch file. Similar to this tutorial, just start the launch file in one terminal:
roslaunch hector_slam_launch postproc_qut_logs.launch
and then play back your bagfile in another terminal:
rosbag play 2.5D_bag02.bag --clock
Thank you for reply. I tried to run with hector_mapping but it keeps complaining "lookupTransform base_footprint to laser timed out. Could not transform laser scan into base_frame." I might need time to run it with. If you could run it with the linked bag file, it would be great to see results.
The bag file link is https://dl.dropbox.com/u/12446150/2.5D_bag02.bag Thank you.
I've had problems using laser scan matcher in hallways as well, although the angular errors in your video are different than what weve seen.
Normally laser based ICP will fail by shortening the end wall as you approach, and lengthening it as you move away.
I think this is because, due to the nature of a 2D laser scanner, you will have points more densely packed closer to the robot than farther away down the wall, so ICP will tend to skew toward matching the closer points than the ones farther out.
If you have other odom sensors, try using something like robot_pose_ekf and adjust the covariances of your laser odom.
Well i can confirm that Hector Slam is really stable and robust. It is even that stable that you can use it on a Helicopter (Octocopter) like we did. Take a look here.
More information could be found
http://www.youtube.com/watch?v=i2UIN-bkGe8&feature=player_detailpage
Cheers.
I could map entire large area with hector_mapping. Thank you for launch file and the self enplaning tutorial. I think it would be good to public if you could include this bag file and launch file to your repo then other ppl could have more idea from it. All bag files are free to use with copyrights. In addition, this would be good comparison with laser_scan_matcher(scan_tool) and gmapping since they were failed this particular environment(two parallel walls.). I also could generate demonstration footage for comparison. Cheers,
Inkyu.
As you mentioned before, something happens at the end of the hallway right corner(Please have a look the picture) but sometimes it works and creates nice map. Do you have any idea about it? Cheers.
Yes, that is the fault I was also seeing occassionally. If the bag is played back at lower speed or stepped through, this does not appear to happen. Can you check if it works better when you increase the scan queue size even more above 25?
I changed scan queue size as 100 to 1000 but still failed. Instead you could find a large bag file that works fine with hector_mapping at http://dl.dropbox.com/u/12446150/2.5D_bag03.bag
Also, it would be great if we could share this with the public then could get more idea. I have a question about height mapping. I want to generate 2.5D map with this bag file since there is already height information. Do Hector_mapping already support this such similar to this.
Asked: 2012-06-04 21:38:08 -0500
Seen: 3,622 times
Last updated: Jun 25 '12
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.
