Tightly-coupled LiDAR-camera

A LiDAR-camera SLAM system is tightly coupled when point cloud registration residuals and visual residuals are optimized jointly in a single cost function (or a single filter update) over one shared state. It is loosely coupled when each modality runs its own odometry and only the resulting pose estimates are fused afterwards, e.g., in a pose graph or a simple filter.

The joint problem

In a tightly-coupled optimization backend, the state X\mathbf{X} (poses, velocities, IMU biases, sometimes landmarks) minimizes a sum of heterogeneous terms:

X=argminX  rIMUΣI2+rvisualΣV2+rLiDARΣL2+rloopΣlp2\mathbf{X}^* = \arg\min_{\mathbf{X}} \; \sum \|\mathbf{r}^{\text{IMU}}\|^2_{\Sigma_I} + \sum \|\mathbf{r}^{\text{visual}}\|^2_{\Sigma_V} + \sum \|\mathbf{r}^{\text{LiDAR}}\|^2_{\Sigma_L} + \sum \|\mathbf{r}^{\text{loop}}\|^2_{\Sigma_{lp}}

where LiDAR residuals are typically point-to-plane or point-to-line distances, and visual residuals are reprojection or photometric errors. LVI-SAM realizes this with a factor graph on GTSAM. The filter-based equivalent puts the same residuals into an iterated Kalman update: FAST-LIVO stacks the Jacobians of both modalities, H=[HLiDAR;HVisual]\mathbf{H} = [\mathbf{H}^{\text{LiDAR}}; \mathbf{H}^{\text{Visual}}], into one update, while FAST-LIVO2 applies them sequentially within one iteration — LiDAR first, then vision on the intermediate state — to handle the very different dimensionalities of a LiDAR scan and an image.

By contrast, a loosely-coupled design would run LiDAR odometry and visual odometry independently and fuse only their 6-DoF pose outputs. That compression is exactly what tight coupling avoids.

Tight vs loose at a glance

Tightly coupledLoosely coupled
What is fusedraw residuals (points, pixels)6-DoF pose estimates (+ covariance)
Information retentionfull — cross-correlations with biases keptlossy — each modality pre-marginalized
Cross-modal aidingautomatic through the shared stateonly via hand-designed interfaces
Sensitivity to calibration errorshigh — errors enter every residuallower — absorbed per subsystem
Failure isolationpoor by default — outliers corrupt the joint stategood — a failing odometry can be ignored
Implementation efforthighlow

Why bother with the extra complexity?

Common pitfalls

Why it matters for SLAM

The tight-vs-loose distinction, familiar from VIO, is the single most important architectural axis in LiDAR-camera fusion: it largely determines a system’s accuracy ceiling and its failure behavior. Every major LVI system (LVI-SAM, R3LIVE, FAST-LIVO2) advertises tight coupling as a headline feature, and reading their cost functions is the fastest way to understand what each system actually fuses.