It has proven to be robust for different sensor setups and environments without the need of an initial guess.
We use a FPFH-based feature vector creation with an TEASER++ feature matching for the coarse alignment, which is used as initial guess for the GICP algorithm.
Motion- and targetless multi - LiDAR-to-LiDAR Calibration Pipeline,
developed at the Institute of Automotive Technology, TUM
- Our tool was specifically developed for motionless calibration.
- We assume that each LiDAR to be calibrated has either a directly overlapping FOV with the target LiDAR FOV or has overlap with other LiDAR(s) with overlap to the target. This can be cascading dependency to the target.
- We assume that the ground is flat and the environment is static.
- Input point clouds for the calibration are in sensor_msgs/PointCloud2 or in .pcd format.
-
Build the Docker image:
./docker/build_docker.sh -
Run the container:
./docker/run_docker.sh
-
Install ROS2 humble (might work with other ROS2 distributions but wasn't tested): https://docs.ros.org/en/humble/Installation.html
-
Create a ROS 2 workspace:
mkdir -p ~/ros2_ws cd ~/ros2_ws -
Clone the repository:
git clone [email protected]:TUMFTM/Multi_LiCa.git -
Install dependencies:
cd Multi_LiCa pip install --no-cache-dir --upgrade pip pip install --no-cache-dir -r requirements.txt -
Source the ROS 2 environment and build the project using
colcon:source /opt/ros/$ROS_DISTRO/setup.bash colcon build --symlink-install --packages-up-to multi_lidar_calibrator --cmake-args -DCMAKE_BUILD_TYPE=Release
-
Configure the parameters to fit your data:
vim config/<params-file>.yaml -
Launch the multi_lidar_calibrator node:
ros2 launch multi_lidar_calibrator calibration.launch.py parameter_file:=/path/to/parameter/file
-
We provided a detailed parameter file with explanation with
config/params.yaml -
Configure
config/params.yamlto fit your data. Depending on the application, you may need to specify the LiDARs, paths to .pcd files, or LiDAR topic names. You may also change GICP and RANSAC parameters. -
In addition to LiDAR-to-LiDAR calibration, you can perform target LiDAR-to-ground/base calibration if your x,y translation and roll, yaw rotation are precisely known.
If you are using to-base calibration, you may choose a URDF file to save the calibration so that it can be directly used in your ROS robot-state-publisher. -
When running in a container, ensure that your local and container environments have the same ROS_DOMAIN_ID. If not, set it to be the same with
export ROS_DOMAIN_ID=<ID>. -
When using ROS 2, verify that the transformation guess is published on the
/tf_statictopic and that the data is published for all specified LiDARs.
On default, the tool will launch a demo with data from OpenCalib.
It will open a window and will display three pointclouds and their initial transforms. You can inspect the files in the interactive window. After closing the window (press Q), the tool will calculate the transformations ans will print the results to the terminal, write them to the output directory and will display a windows with the transformed pointclouds.