ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I just tried RGBDSlam a few weeks ago as a handheld scanner with very bad results. The error drift is increasing dramatically which will result in very badly aligned scan matches. Another problem is, that this algo uses rgb information only for scan matching, so if your room doesn't provide enough features, the internal scan matcher (ICP I guess) will not work. Also there is a memory cap which will crash the program without warning. The kinfu largscale from pcs (you need to checkout pcl unstable and compile from source) worked much better, but requires at least 2GB GPU-Ram

I just tried RGBDSlam a few weeks ago as a handheld scanner with very bad results. The error drift is increasing dramatically which will result in very badly aligned scan matches. Another problem is, that this algo uses rgb information only for scan matching, so if your room doesn't provide enough features, the internal scan matcher (ICP I guess) will not work. work properly. Also there is a memory cap which will crash the program without warning. The kinfu largscale from pcs pcl (you need to checkout pcl unstable and compile from source) worked much better, but requires at least 2GB GPU-Ram

I just tried RGBDSlam a few weeks ago as a handheld scanner with very bad results. The error drift is increasing dramatically which will result in very badly aligned scan matches. Another problem is, that this algo uses rgb information only for scan matching, so if your room doesn't provide enough features, the internal scan matcher (ICP I guess) will not work properly. Also there is a memory cap which will crash the program without warning. The kinfu largscale from pcl (you need to checkout pcl unstable and compile from source) worked much better, but requires at least 2GB GPU-Ram

(unbiased suggestion)