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

IMU-Lidar timestamp issue #124

Open
Efesendil opened this issue Dec 5, 2024 · 1 comment
Open

IMU-Lidar timestamp issue #124

Efesendil opened this issue Dec 5, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Efesendil
Copy link

Hello,
I am getting inconsistent (the map drifts after a while) results while using imu and lidar together in carla sim, what could be the issue for the warnings below ?

[2024-12-05 01:03:42.608] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)
[2024-12-05 01:03:42.608] [odom] [warning] t_last=179.920230 t_current=179.970230 num_imu=1
[2024-12-05 01:03:42.681] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)
[2024-12-05 01:03:42.681] [odom] [warning] t_last=179.970230 t_current=180.020230 num_imu=1
[2024-12-05 01:03:42.751] [odom] [warning] insufficient number of IMU data between LiDAR scans!! (odometry_estimation)
[2024-12-05 01:03:42.751] [odom] [warning] t_last=180.020230 t_current=180.070230 num_imu=1

@Efesendil Efesendil added the bug Something isn't working label Dec 5, 2024
@Efesendil
Copy link
Author

Efesendil commented Dec 17, 2024

The problem is in sub_mapping.cpp from line 217 to 242, where the imu preintegration was handled. Probably it is waiting for more frequent imu data in the defined interval (50 miliseconds in my case since the lidar frequency is at 20 hz). However i don't know how to configure carla simulator to publish more frequent imu data than lidar data.
To be able to successfully handle the imu preintegration we should have at least 2 imu inputs in this interval, as we can see from the warnings i only have one, i will try to modify the code to set this number to 1 in order to see if the imu data will be added as a factor into the graph and if the drift still occurs (since carla is a simulation environment, even with 1 imu data it should handle correctly, my imu noise rates are null). One last thing, in this case I think that the scan deskewing won't work as expected, since using one imu data it can't apply the interpolation for the point clouds.
I don't have a clear solution if this problem occurs in such specific cases, probably it is something to do with sensors hardware synchronization and time stamping. Most of the time IMU publishes data at 100hz and lidar at 20hz, so it should work for real hardware :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant