Lab-of-AI-and-Robotics / GS_ICP_SLAM

[ECCV 2024] RGBD GS-ICP SLAM
MIT License
344 stars 36 forks source link

gs_gicp_slam did not work for GS_ICP_SLAM #37

Open huarzail opened 4 months ago

huarzail commented 4 months ago

Hello, all authors.

At first, thank you for your contribution to the open source community.

When I installed the gs_gicp_slam, I run the command"bash tum.sh",it seems that this project endless loop near the code " current_pose =reg.align(poses[-1])" of line 199 in mp_Tracker.py. Some scholar tell me that may be the fast_gicp was not installed correctly.

My machine is Ubuntu-2204.

When I installed the fast_gicp again, I run the example in the python_tester directory(python using_previous_30.py ../../../../datasets/TUM/rgbd_dataset_freiburg3_long_office_household tum 0.05 false). It breaked, the log is "Segmentation fault (core dumped)". Also caused by the code "current_pose = reg.align(poses[-1])".

Then I use the gdb debug, the log is:

Thread 43 "python" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff48f62640 (LWP 2740189)] 0x00007fffc3b0221c in bool fast_gicp::FastGICP<pcl::PointXYZ, pcl::PointXYZ, pcl::search::KdTree<pcl::PointXYZ, pcl::KdTreeFLANN<pcl::PointXYZ, flann::L2_Simple > >, pcl::search::KdTree<pcl::PointXYZ, pcl::KdTreeFLANN<pcl::PointXYZ, flann::L2_Simple > > >::calculate_source_covariances_with_filter(pcl::PointCloud::ConstPtr const&, pcl::search::Search&, std::vector<Eigen::Matrix<double, 4, 4, 0, 4, 4>, Eigen::aligned_allocator<Eigen::Matrix<double, 4, 4, 0, 4, 4> > >&, std::vector<float, std::allocator >&, std::vector<float, std::allocator >&, std::vector<int, std::allocator >&) [clone ._omp_fn.0] () from /home/gvlib_ljh/3DGS-SLAM/GS_ICP_SLAM/submodules/fast_gicp_slam/build/lib.linux-x86_64-cpython-310/libfast_gicp.so

Will you can tell me how to fix this error.

Thanks.

Aaron-0303 commented 3 weeks ago

I also encountered the same problem. May I ask if it has been resolved?

Justzhongjj commented 5 days ago

I also encountered the same problem, too. May I ask if it has been resolved?