LI-Init is a robust, real-time initialization method for LiDAR-inertial system. The proposed method calibrates the temporal offset and extrinsic parameter between LiDARs and IMUs, and also the gravity vector and IMU bias. Our method does not require any target or extra sensor, specific structured environment, prior environment point map or initial values of extrinsic and time offset. Our package address following key issues:
- A robust LiDAR odometry (Fast LO) modified from FAST-LIO2.
- Fast and robust temporal offset and extrinsic parameter calibration between LiDAR and IMU without any hardware setup.
- Support multiple LiDAR types: both mechanical spinning LiDAR (Hesai, Velodyne, Ouster) and solid-state LiDAR ( Livox Avia/Mid360)
- Seamlessly merged into FAST-LIO2, as a robust initialization module.
Contributors: Fangcheng Zhu 朱方程， Yunfan Ren 任云帆， Wei Xu 徐威， Yixi Cai 蔡逸熙
our related papers are now available on arxiv: Robust Real-time LiDAR-inertial Initialization
If our code is used in your project, please cite our paper following the bibtex below:
@article{zhu2022robust,
title={Robust Real-time LiDAR-inertial Initialization},
author={Zhu, Fangcheng and Ren, Yunfan and Zhang, Fu},
journal={arXiv preprint arXiv:2202.11006},
year={2022}
}
our accompanying videos are now available on YouTube (click below images to open) and Bilibili.
Ubuntu >= 18.04.
ROS >= Melodic. ROS Installation
PCL >= 1.8, Follow PCL Installation.
Eigen >= 3.3.4, Follow Eigen Installation.
Follow livox_ros_driver Installation.
Remarks:
- Since the LI_Init must support Livox serials LiDAR firstly, so the livox_ros_driver must be installed and sourced before run any LI_Init luanch file.
- How to source? The easiest way is add the line
source $Livox_ros_driver_dir$/devel/setup.bashto the end of file~/.bashrc, where$Livox_ros_driver_dir$is the directory of the livox_ros_driver workspace (should be thews_livoxdirectory if you completely followed the livox official document).
Our code has been tested on ceres-solver-2.0.0. Please download ceres-solver following the instructions.
When you use Docker, you could solve the prerequisites above at once.
For more information, you can check docker_start.md.
Clone the repository and catkin_make:
cd ~/catkin_ws/src
git clone https://github.com/hku-mars/LiDAR_IMU_Init.git
cd ..
catkin_make
source devel/setup.bash
Please make sure the parameters in config/xxx.yaml are correct before running the project.
It is highly recommended to run LI-Init and record your own data simultaneously, because our algorithm is able to automatically detect the degree of excitation and instruct users how to give sufficient excitation (e.g. rotate or move along which direction).
Theoretically livox_avia.launch supports mid-70, mid-40 LiDARs.
Note: The code of LI-Init contains the initialization module and sequential FAST-LIO. If you run the code of LI-Init, it will first do initialization (if suffienct excitation is given, it will tell you the extrinsic transformation and temporal offset) and then it will switch into FAST-LIO. Thus, if you want to run FAST-LIO on your own data but unfortunately the LiDAR and IMU are not synchronized or calibrated before, you can directly run LI-Init. As for R3LIVE, you can write the extrinsic and temporal offset between LiDAR and IMU obtained by LI-Init into the config file of R3LIVE.
Edit config/xxx.yaml to set the below parameters:
-
lid_topic: Topic name of LiDAR pointcloud. -
imu_topic: Topic name of IMU measurements. -
cut_frame_num: Split one frame into sub-frames, to improve the odom frequency. Must be positive integers. -
orig_odom_freq(Hz): Original LiDAR input frequency. For most LiDARs, the input frequency is 10 Hz. It is recommended that cut_frame_num * orig_odom_freq = 30 for mechinical spinning LiDAR, cut_frame_num * orig_odom_freq = 50 for livox LiDARs. -
mean_acc_norm($m/s^2$ ): The acceleration norm when IMU is stationary. Usually, 9.805 for normal IMU, 1 for livox built-in IMU. -
data_accum_length: A threshold to assess if the data is enough for initialization. Too small may lead to bad-quality results. -
online_refine_time(second): The time of extrinsic refinement with FAST-LIO2. About 15~30 seconds of refinement is recommended. -
filter_size_surf(meter): It is recommended that filter_size_surf = 0.05~0.15 for indoor scenes, filter_size_surf = 0.5 for outdoor scenes. -
filter_size_map(meter): It is recommended that filter_size_map = 0.15~0.25 for indoor scenes, filter_size_map = 0.5 for outdoor scenes.
After setting the correct topic name and parameters, you can directly run LI-Init with your own data..
cd catkin_ws
source devel/setup.bash
roslaunch lidar_imu_init xxx.launch
After initialization and refinement finished, the result would be written into catkin_ws/src/LiDAR_IMU_Init/result/Initialization_result.txt
Download our test bags here: Lidar IMU Initialization Datasets.
Use rosbag info xxx.bag to get the correct topic name.
Please note: if the tested IMU is Livox built-in IMU, mean_acc_norm should be 1. If the IMU is Pixhawk IMU, mean_acc_norm should be 9.805.
Here are the pointcloud map constructed by our LiDAR odometry (FAST-LO).
Thanks for HKU MaRS Lab, Fast-LIO2 (Fast Direct LiDAR-inertial Odometry) and ikd-tree.
Thanks for Livox Technology for equipment support.
The most important parameters for FAST-LIO are the extrinsic rotation and translation matrix, and the time offset.
For the same device setup (the relative pose between IMU and LiDAR is fixed), you can just write the extrinsic into FAST-LIO's configuration file.
As for time offset, it depends on the synchronization mechanism of the lidar and IMU. For pixhawk IMU, as far as I know, the timestamp is PC time. If the lidar's timestamp is also PC time, then the time offset might be the same. You can bypass temporal initialization next time. But for some lidars like Livox avia/horizon, the timestamp origin is the moment when the lidar is powered on. So, if you power it off and power it on again, the timestamp counts from 0. In this condition, temporal initialization is necessary at each time the lidar is powered on. So, you can run LI-Init once, record the time offset; then power off the lidar and IMU for minutes, then power on them and calibrate time offset again. If the time offset are close, it means you may bypass time offset initialization next time. Just write down the time offset into time_diff_lidar_to_imu of FAST-LIO's configuration file.
As for IMU bias and gravity, FAST-LIO can refine them online. You don't need to write these prameters.
The source code is released under GPLv2 license.
We are still working on improving the performance and reliability of our codes. For any technical issues, please contact us via email zhufc@connect.hku.hk. For commercial use, please contact Dr. Fu Zhang fuzhang@hku.hk.