-
Notifications
You must be signed in to change notification settings - Fork 956
Issues: laboshinl/loam_velodyne
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
How to tune params to avoid the terrible performance on other dataset?
#143
opened Aug 1, 2019 by
LiShuaixin
Is the direction of robot walking related to the performance of mapping or location?
#142
opened Jul 22, 2019 by
yuekaka
How to use the algorithm for lidar mapping with a horizontal scanning angle of 120°?
#133
opened Apr 24, 2019 by
LiaoJunchan
Bug? the for loop upper bound is not correct when search corner point in last sweep
#124
opened Mar 19, 2019 by
Bzhnja
Are there any comparisions of LOAM and other 3D lidar SLAM algorithm?
#123
opened Feb 24, 2019 by
sunhao-seu
Publishing rate of the /veloydne_points topic may affect the KITTI Dataset odometry results
#117
opened Jan 21, 2019 by
claydergc
Lidar Odometry: Computation of a bisquare weight of feature points
#114
opened Jan 11, 2019 by
claydergc
pass the mapping result back as a start position for odometry?
#113
opened Jan 10, 2019 by
antithing
ProTip!
What’s not been updated in a month: updated:<2024-06-25.