RobustFieldAutonomyLab / LeGO-LOAM

LeGO-LOAM: Lightweight and Ground-Optimized Lidar Odometry and Mapping on Variable Terrain
BSD 3-Clause "New" or "Revised" License
2.38k stars 1.11k forks source link

Problems with VLP-16 dataset w/ IMU #24

Closed ojura closed 5 years ago

ojura commented 6 years ago

Hi! Would you have a moment to take a look at the dataset provided here? https://ferhr-my.sharepoint.com/:f:/g/personal/jorsulic_fer_hr/EvwbIJ1tVipLqAJi1ECinDcBLLwKVF0Vki1m4zQ6ye0Jwg?e=TqqWCu

To run Lego-LOAM with the dataset:

rosrun imu_filter_madgwick imu_filter_node /imu/data_raw:=imu _publish_tf:=false _use_mag:=false _gain:=0.005
roslaunch lego_loam run.launch
rosbag play processed_type1_traderjoes.bag  points2_1_VLP16:=/velodyne_points --clock

The trajectory sometimes looks okay piecewise, but often has jerky moments. Also, in the second part of processed_type1_traderjoes.bag, the trajectory goes crazy, up in the air, with an arbitrary pitch and roll - it looks like the gravity measured by the IMU is ignored. As far as I can tell, the IMU is well aligned to the lidar (~< 0.5 degrees). Do you maybe know what could be the cause?

(You may have to install the Madgwick filter with sudo apt install ros-melodic-imu-filter-madgwick.)

Also: the frequency is 20 Hz, which means the angular resolution is 0.4 degrees. However, If I tried adjusting for this (the angular resolution), I would get a crash.

ojura commented 5 years ago

Hi @TixiaoShan, is there a chance you could take a look?

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.