Papers › AlignMiF: Geometry-Aligned Multimodal Implicit Field for LiDAR-Camera Joint Synthesis

AlignMiF: Geometry-Aligned Multimodal Implicit Field for LiDAR-Camera Joint Synthesis

27 Feb 2024CVPR 2024 1arXiv:2402.17483archive 2025-07-28

Tao Tang, Guangrun Wang, Yixing Lao, Peng Chen, Jie Liu, Liang Lin, Kaicheng Yu, Xiaodan Liang

Neural implicit fields have been a de facto standard in novel view synthesis. Recently, there exist some methods exploring fusing multiple modalities within a single field, aiming to share implicit features from different modalities to enhance reconstruction performance. However, these modalities often exhibit misaligned behaviors: optimizing for one modality, such as LiDAR, can adversely affect another, like camera performance, and vice versa. In this work, we conduct comprehensive analyses on the multimodal implicit field of LiDAR-camera joint synthesis, revealing the underlying issue lies in the misalignment of different sensors. Furthermore, we introduce AlignMiF, a geometrically aligned multimodal implicit field with two proposed modules: Geometry-Aware Alignment (GAA) and Shared Geometry Initialization (SGI). These modules effectively align the coarse geometry across different modalities, significantly enhancing the fusion process between LiDAR and camera data. Through extensive experiments across various datasets and scenes, we demonstrate the effectiveness of our approach in facilitating better interaction between LiDAR and camera modalities within a unified neural field. Specifically, our proposed AlignMiF, achieves remarkable improvement over recent implicit fusion methods (+2.01 and +3.11 image PSNR on the KITTI-360 and Waymo datasets) and consistently surpasses single modality performance (13.8% and 14.2% reduction in LiDAR Chamfer Distance on the respective datasets).

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 10 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 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: 10 samples from 1 repository, 8 ran (5 with no instrument failure; 3 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tangtaogo/alignmif officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 8 ran (3 instrument-failed) · 2 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

10 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 2 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 · our draft was wrong
2ran; the contract check could not run
5ran
2unverified

Licence: 1 of the 10 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from tangtaogo/alignmif. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

tangtaogo/alignmif official repository 10 samples, 8 ran (3 instrument-failed) · 2 unverified
dice_coeff in 14 papers lidarnvs/unet.py ran MIT (permissive) · c1cb6e3e76067a5d · report fixture: signature input:Tensor/3/float, target:Tensor/3/float, reduce_batch_first:bool/0/bool, epsilon:float/0/float · returned Tensor · level recorded 2026-09-24
dice_loss in 193 papers
census: 10 implementations from 16 papers, 7 distinct outputs across 4 buckets, one shared input per bucket
lidarnvs/unet.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 02b5df44eb5c21a3 · report fixture: signature input:Tensor/4/float, target:Tensor/4/float, multiclass:bool/0/bool · returned Tensor · level recorded 2026-09-24
find_closest_label lidarnerf/convert.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · cfac707d99413ea6 · report fixture: signature beam_labels:list/1/float, angle:float/0/float · returned int · level recorded 2026-09-24
fscore in 10 papers extern/fscore.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · 1929a5b8c241cd48 · report fixture: signature dist1:Tensor/2/float, dist2:Tensor/2/float, threshold:float/0/float · returned tuple · level recorded 2026-09-24
huber_loss in 34 papers
census: 6 implementations from 7 papers, 5 distinct outputs across 5 buckets, one shared input per bucket
lidarnerf/loss.py ran fingerprinted MIT (permissive) · 00979fadb02bf8df · report fixture: signature pred:Tensor/2/float, target:Tensor/2/float, delta:float/0/float, reduction:str/0/str · returned Tensor · level recorded 2026-09-24
lidar_to_pano_with_intensities lidarnerf/convert.py ran MIT (permissive) · 6657e863031cc206 · report fixture: signature local_points_with_intensities:ndarray/2/float, lidar_H:int/0/int, lidar_W:int/0/int, lidar_K:tuple/1/float, beam_inclinations:ndarray/1/float, max_depth:int/0/int · returned tuple · level recorded 2026-09-24
mape_loss in 8 papers lidarnerf/loss.py ran fingerprinted MIT (permissive) · ddcd1a350d11a260 · report fixture: signature pred:Tensor/2/float, target:Tensor/2/float, reduction:str/0/str · returned Tensor · level recorded 2026-09-24
multiclass_dice_coeff lidarnvs/unet.py ran · our draft was wrong MIT (permissive) · 9445687b9106e2f8 · report fixture: signature input:Tensor/4/float, target:Tensor/4/float, reduce_batch_first:bool/0/bool, epsilon:float/0/float · returned Tensor · level recorded 2026-09-24
get_encoder in 45 papers lidarnerf/encoding.py unverified MIT (permissive) · 0eaf72cf098311a6 · report
lidar_to_pano_with_intensities_with_bbox_mask lidarnerf/convert.py unverified MIT (permissive) · fcd40c17509b87bd · report

Tasks

Novel View Synthesis

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ALIGN

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