-
Notifications
You must be signed in to change notification settings - Fork 20
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
did you use inbuilt IMU's from Ouster and Livox for mapping? #9
Comments
hanks for your interest in our dataset. |
@Qingq-li , Thanks, can you explain how you did Lidar-IMU calibration? |
Hi, the extrinsic parameter between each lidar and its build-in IMU is public available from factory instruction. For the intrinsic of IMU, methods like LIO-Livox and Fast LIO will estimate the biases and noise distribution automatically. Therefore, we don't have to calibrate by ourselves if we just want to compare performance between different methods with parameters from the factory and STOA SLAM methods. Furthermore, we also calibrate and verify the extrinsic and intrinsic parameters with open-source calibration tools. Here, I recommend one targetless calibration tool, LIDAR_IMU_INIT (https://github.com/hku-mars/LiDAR_IMU_Init), which is easy to use and the code is well-organized. |
@Qingq-li , I have used LIDAR_IMU_INIT, but not getting good results as my lidar and imu are already mounted on a wheeled robot |
Could we use velodyne lidar data running with livox imu data for lio-sam? |
Hi, unfortunately, as the built-in IMU of LIVOX and Ouster are both 6-axis IMUs, we cannot use it directly on LIO-SAM (https://github.com/TixiaoShan/LIO-SAM) which only works with a 9-axis IMU. |
There is 6axis version of liosam |
Another follow-up question I found recently is the timestamp of velodyne lidar data is quite different from that of livox ima data. Didn’t they record simultaneously? |
|
啊这 |
No description provided.
The text was updated successfully, but these errors were encountered: