Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mapOptimization crashes when robot starts moving #280

Open
astef3 opened this issue Jan 17, 2024 · 0 comments
Open

mapOptimization crashes when robot starts moving #280

astef3 opened this issue Jan 17, 2024 · 0 comments

Comments

@astef3
Copy link

astef3 commented Jan 17, 2024

Hi,
first of all I want to say that you did amazing job with the algorithm and its really nice work. However I have experienced some issue that I was not able to fix.

I have integrated LeGO-LOAM in my ROS workspace on Noetic, Ubuntu 20.04 by following the tutorial at https://www.reddit.com/r/ROS/comments/13tqq7a/3d_slam_with_lego_loam_ros_noetic/.

At first, when I was running it everything was working perfectly, the estimated odometry was extremely good and also the mapping was really detailed, which was amazing. However, currently when I run the algorithm I get some weird behaviour. So I am running the command:
roslaunch lego_loam run.launch
And everything seems to set up nicely, as shown on the image delow:
Screenshot from 2024-01-17 14-19-55

Then I run the following command in order to play my Point Cloud from rosbag file:
rosbag play velodyne_points.bag --clock --topic /velodyne_points
And when the robot starts moving (point cloud message is being played), the algorithm crashed with the exception displayed in the image bellow:

Screenshot from 2024-01-17 14-23-57

Now I did a little debugging and as far as I have understood, the algorithm crashes, when it comes to this part of the code in mapOptimatization.cpp:

isam->update(gtSAMgraph, initialEstimate);
isam->update();
gtSAMgraph.resize(0);
initialEstimate.clear();

More specifically in the : isam->update(gtSAMgraph, initialEstimate); line.

I would really appreciate if anyone can help me with this issue! Thank you in advance and in case anyone needs more information or data in order to recreate the issue I will deliver it right away!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant