hku-mars / livox_camera_calib

This repository is used for automatic calibration between high resolution LiDAR and camera in targetless scenes.
GNU General Public License v2.0
911 stars 207 forks source link

Process dies on LiDAR edge extraction #3

Closed VisionaryMind closed 3 years ago

VisionaryMind commented 3 years ago

I have setup an environment with Ubuntu 18.04 and ROS Melodic. All dependencies have been installed, however, using your sample ROS bag files, I am not able to get past the Lidar edge extraction phase. Here is the terminal output:

Camera Matrix: 
[1364.45, 0, 958.327;
 0, 1366.46, 535.074;
 0, 0, 1]
Distortion Coeffs: 
[0.0958277;
 -0.198233;
 -0.000147133;
 -0.000430056;
 0]
Init extrinsic: 
[0, -1, 0, 0;
 0, 0, -1, 0;
 1, 0, 0, 0;
 0, 0, 0, 1]
[ INFO] [1617231323.709287053]: Loading the rosbag /home/visionarymind/Documents/scans/livoxcalib/outdoor1.bag
[ INFO] [1617231328.493049027]: Sucessfully load Point Cloud and Image
[ INFO] [1617231328.493564736]: Building Voxel
[ INFO] [1617231357.841487217]: Extracting Lidar Edge
[lidar_camera_calib-2] process has died [pid 2586, exit code -11, cmd /home/visionarymind/vision_ws/devel/lib/livox_camera_calib/lidar_camera_calib /home/visionarymind/vision_ws/src/livox_camera_calib/config/camera.yaml /home/visionarymind/vision_ws/src/livox_camera_calib/config/config_outdoor.yaml /home/visionarymind/Documents/scans/livoxcalib/outdoor1.bag /home/visionarymind/vision_ws/src/livox_camera_calib/result __name:=lidar_camera_calib __log:=/home/visionarymind/.ros/log/2c3b8fe2-9274-11eb-9545-000c29df74c2/lidar_camera_calib-2.log].
log file: /home/visionarymind/.ros/log/2c3b8fe2-9274-11eb-9545-000c29df74c2/lidar_camera_calib-2*.log

Would you have any advice on how to correct this problem?

ChongjianYUAN commented 3 years ago

I have setup an environment with Ubuntu 18.04 and ROS Melodic. All dependencies have been installed, however, using your sample ROS bag files, I am not able to get past the Lidar edge extraction phase. Here is the terminal output:

Camera Matrix: 
[1364.45, 0, 958.327;
 0, 1366.46, 535.074;
 0, 0, 1]
Distortion Coeffs: 
[0.0958277;
 -0.198233;
 -0.000147133;
 -0.000430056;
 0]
Init extrinsic: 
[0, -1, 0, 0;
 0, 0, -1, 0;
 1, 0, 0, 0;
 0, 0, 0, 1]
[ INFO] [1617231323.709287053]: Loading the rosbag /home/visionarymind/Documents/scans/livoxcalib/outdoor1.bag
[ INFO] [1617231328.493049027]: Sucessfully load Point Cloud and Image
[ INFO] [1617231328.493564736]: Building Voxel
[ INFO] [1617231357.841487217]: Extracting Lidar Edge
[lidar_camera_calib-2] process has died [pid 2586, exit code -11, cmd /home/visionarymind/vision_ws/devel/lib/livox_camera_calib/lidar_camera_calib /home/visionarymind/vision_ws/src/livox_camera_calib/config/camera.yaml /home/visionarymind/vision_ws/src/livox_camera_calib/config/config_outdoor.yaml /home/visionarymind/Documents/scans/livoxcalib/outdoor1.bag /home/visionarymind/vision_ws/src/livox_camera_calib/result __name:=lidar_camera_calib __log:=/home/visionarymind/.ros/log/2c3b8fe2-9274-11eb-9545-000c29df74c2/lidar_camera_calib-2.log].
log file: /home/visionarymind/.ros/log/2c3b8fe2-9274-11eb-9545-000c29df74c2/lidar_camera_calib-2*.log

Would you have any advice on how to correct this problem?

What is the PCL version you are using? Maybe you should use PCL1.7

VisionaryMind commented 3 years ago

What is the PCL version you are using? Maybe you should use PCL1.7

We were able to get this working by installing a virtual machine with Ubuntu 16.04 and PCL 1.7, so it is clear that later PCL versions can be a problem.

You mentioned in the specs that this can work, however, on Ubuntu 18.04, but Bionic's repo only has PCL 1.8, and it is not possible to compile and install PCL 1.7 on Bionic due to other dependency problems with Eigen, Boost and FLANN, for example. If you have an 18.04 system working, please be so kind as to share your config (conda list or pip freeze). It could be we just need to align the dependencies properly.

For now, we are fine using Ubuntu 16.04 / PCL 1.7, but I would be interested in better understanding how to port this amazing tool over to newer platforms with more up-to-date dependencies. I wish to congratulate you on this superb work. It is one of the most innovative approaches to extrinsics calibration to date and will help our work / research immensely. Thank you for sharing your research with the community.

ChongjianYUAN commented 3 years ago

What is the PCL version you are using? Maybe you should use PCL1.7

We were able to get this working by installing a virtual machine with Ubuntu 16.04 and PCL 1.7, so it is clear that later PCL versions can be a problem.

You mentioned in the specs that this can work, however, on Ubuntu 18.04, but Bionic's repo only has PCL 1.8, and it is not possible to compile and install PCL 1.7 on Bionic due to other dependency problems with Eigen, Boost and FLANN, for example. If you have an 18.04 system working, please be so kind as to share your config (conda list or pip freeze). It could be we just need to align the dependencies properly.

For now, we are fine using Ubuntu 16.04 / PCL 1.7, but I would be interested in better understanding how to port this amazing tool over to newer platforms with more up-to-date dependencies. I wish to congratulate you on this superb work. It is one of the most innovative approaches to extrinsics calibration to date and will help our work / research immensely. Thank you for sharing your research with the community.

Thank you for your attention. The program will be compatible with the latest version of PCL in the near future, expected in one or two weeks.

Cenbylin commented 3 years ago

Has the compatibility upgrade been completed? I use ubuntu18 + pcl1.9, then I meet the same problem.

Thank you for the impressive project.

sheng00125 commented 2 years ago

I meet the same problem on ubuntu18 + pcl1.8.

chengfzy commented 2 years ago

same problem!

Chatoyant19 commented 1 year ago

I solved this prolem. just modified pcl version to the sysytem default version. eg, ubuntu 20.04 + pcl-1.10

zayedrmdn commented 3 months ago

@Chatoyant19 what did you modified exactly?