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

will LIVO2 optimize the Extrinsics between lidar with camera #23

Open
jiachenglihxl opened this issue Sep 15, 2024 · 3 comments
Open

will LIVO2 optimize the Extrinsics between lidar with camera #23

jiachenglihxl opened this issue Sep 15, 2024 · 3 comments

Comments

@jiachenglihxl
Copy link

jiachenglihxl commented Sep 15, 2024

In the papar, LIVO2 uses lidar points to generate visual map, the extrinsics will be very important. Will LIVO2 solve this issue?

@xuankuzcr
Copy link
Member

We will pre-calibrate the pixel-level extrinsic parameters, but we won’t optimize them online as it is prone to negative optimization. In r3live, both the intrinsic and extrinsic parameters are optimized online, with negative optimization being quite evident. I believe an initialization module (e.g., VINS-mono) is quite necessary in the absence of accurate extrinsic parameters.

@jiachenglihxl
Copy link
Author

Thanks! VINS-mono will able to optimize camera extrinsic between IMU. In r3live, I feel we actually get camera or lidar extrinsic between IMU, not the extrinsic beteen camera with lidar directly.
However in LIVO system, we can get lidar and camera feature together. So is it possible to use this feature to optimize extrinsic between camera with lidar directly?

@xuankuzcr
Copy link
Member

In LIVO2, the image reference patch is attached to the LiDAR plane. It might be possible to optimize the extrinsic parameters between the camera and LiDAR by minimizing the photometric error of multi-frame observations of the reference patch, leveraging the plane prior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants