Papers › Differentiable Registration of Images and LiDAR Point Clouds with VoxelPoint-to-Pixel Matching

Differentiable Registration of Images and LiDAR Point Clouds with VoxelPoint-to-Pixel Matching

7 Dec 2023NeurIPS 2023 11arXiv:2312.04060archive 2025-07-28

Junsheng Zhou, Baorui Ma, Wenyuan Zhang, Yi Fang, Yu-Shen Liu, Zhizhong Han

Cross-modality registration between 2D images from cameras and 3D point clouds from LiDARs is a crucial task in computer vision and robotic. Previous methods estimate 2D-3D correspondences by matching point and pixel patterns learned by neural networks, and use Perspective-n-Points (PnP) to estimate rigid transformation during post-processing. However, these methods struggle to map points and pixels to a shared latent space robustly since points and pixels have very different characteristics with patterns learned in different manners (MLP and CNN), and they also fail to construct supervision directly on the transformation since the PnP is non-differentiable, which leads to unstable registration results. To address these problems, we propose to learn a structured cross-modality latent space to represent pixel features and 3D features via a differentiable probabilistic PnP solver. Specifically, we design a triplet network to learn VoxelPoint-to-Pixel matching, where we represent 3D elements using both voxels and points to learn the cross-modality latent space with pixels. We design both the voxel and pixel branch based on CNNs to operate convolutions on voxels/pixels represented in grids, and integrate an additional point branch to regain the information lost during voxelization. We train our framework end-to-end by imposing supervisions directly on the predicted pose distribution with a probabilistic PnP solver. To explore distinctive patterns of cross-modality features, we design a novel loss with adaptive-weighted optimization for cross-modality feature description. The experimental results on KITTI and nuScenes datasets show significant improvements over the state-of-the-art methods. The code and models are available at https://github.com/junshengzhou/VP2P-Match.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 12 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 7 ran (3 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 7 samples that ran have no recorded date.

junshengzhou/vp2p-match officialmentioned in papermentioned on GitHubpytorchSyntology: 12 samples, 7 ran (4 instrument-failed) · 5 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

12 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
2ran · our draft was wrong
2ran; the contract check could not run
2ran
5unverified

Licence: 12 of the 12 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from junshengzhou/vp2p-match. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

junshengzhou/vp2p-match official repository 12 samples, 7 ran (4 instrument-failed) · 5 unverified
conv1x1 in 691 papers models/network_img/resnet.py ran · our draft was wrong no licence file found · pointer only · d9def42110729a85 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded, date not recorded
conv3x3 in 1,376 papers models/network_img/resnet.py ran · our draft was wrong no licence file found · pointer only · 160bb14bd76201b4 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, groups:int/0/int, dilation:int/0/int · returned Conv2d · level recorded, date not recorded
get_P_diff run_kitti.py ran · honoured contract no licence file found · pointer only · 685179cc383d2145 · report fixture: signature P_pred_np:ndarray/2/float, P_gt_np:ndarray/2/float · returned tuple · level recorded 2026-09-24
projection_pc_img models/kitti_dataset.py ran no licence file found · pointer only · 2eaecdd32aa9f550 · report fixture: signature pc_np:ndarray/2/float, img:ndarray/3/int, K:ndarray/2/float, size:int/0/int · returned ndarray · level recorded 2026-09-24
sample_and_group_all in 26 papers models/pointTransformer/utils.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 225a2727f042aed0 · report fixture: signature xyz:Tensor/3/float, points:Tensor/3/float, use_xyz:bool/0/bool · returned tuple · level recorded 2026-09-22
test_acc_trans run_kitti.py ran no licence file found · pointer only · ff34a143e5f7bcd1 · report fixture: signature model:callable/0/?, testdataloader:list/1/dict, args:ArgsConfig/0/? · returned tuple · level recorded 2026-09-24
transform_pc_np models/kitti_dataset.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 2723e9de0f3630bf · report fixture: signature P:ndarray/2/float, pc_np:ndarray/2/float · returned ndarray · level recorded 2026-09-24
adapt_loss utils/loss.py unverified no licence file found · pointer only · 390859e4bb289148 · report
det_loss utils/loss.py unverified no licence file found · pointer only · eb05e8a9a7136d5c · report
fps_subsample models/pointTransformer/utils.py unverified no licence file found · pointer only · 1702ee5f1cc07dfc · report
resnet18 in 432 papers models/network_img/resnet.py unverified no licence file found · pointer only · ad028bc423fed232 · report
sample_and_group in 10 papers models/pointTransformer/utils.py unverified no licence file found · pointer only · 6f2216748fe51adb · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

PnP

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections