You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have several bag files recorded at different altitudes with a UAV, such as 50m, 100m, etc. The LiDAR is positioned at nadir, pointing downward. There is significant odometry degradation, particularly in some areas. I also tested the same bag files with FAST-LIO2, and its performance was better and closer to the ground truth. My question is: do you have any suggestions for adjusting parameters for outdoor use and fixing these degradation points? (I've already adjusted filter_size_surf, etc.) The odometry completely diverges in the opposite direction and fails to recover.
The text was updated successfully, but these errors were encountered:
I have several bag files recorded at different altitudes with a UAV, such as 50m, 100m, etc. The LiDAR is positioned at nadir, pointing downward. There is significant odometry degradation, particularly in some areas. I also tested the same bag files with FAST-LIO2, and its performance was better and closer to the ground truth. My question is: do you have any suggestions for adjusting parameters for outdoor use and fixing these degradation points? (I've already adjusted filter_size_surf, etc.) The odometry completely diverges in the opposite direction and fails to recover.
Can you provide a picture with the results? Thank you!
Hi,
I have several bag files recorded at different altitudes with a UAV, such as 50m, 100m, etc. The LiDAR is positioned at nadir, pointing downward. There is significant odometry degradation, particularly in some areas. I also tested the same bag files with FAST-LIO2, and its performance was better and closer to the ground truth. My question is: do you have any suggestions for adjusting parameters for outdoor use and fixing these degradation points? (I've already adjusted filter_size_surf, etc.) The odometry completely diverges in the opposite direction and fails to recover.
The text was updated successfully, but these errors were encountered: