Papers › LiDAR-NeRF: Novel LiDAR View Synthesis via Neural Radiance Fields

LiDAR-NeRF: Novel LiDAR View Synthesis via Neural Radiance Fields

20 Apr 2023arXiv:2304.10406archive 2025-07-28

Tang Tao, Longfei Gao, Guangrun Wang, Yixing Lao, Peng Chen, Hengshuang Zhao, Dayang Hao, Xiaodan Liang, Mathieu Salzmann, Kaicheng Yu

We introduce a new task, novel view synthesis for LiDAR sensors. While traditional model-based LiDAR simulators with style-transfer neural networks can be applied to render novel views, they fall short of producing accurate and realistic LiDAR patterns because the renderers rely on explicit 3D reconstruction and exploit game engines, that ignore important attributes of LiDAR points. We address this challenge by formulating, to the best of our knowledge, the first differentiable end-to-end LiDAR rendering framework, LiDAR-NeRF, leveraging a neural radiance field (NeRF) to facilitate the joint learning of geometry and the attributes of 3D points. However, simply employing NeRF cannot achieve satisfactory results, as it only focuses on learning individual pixels while ignoring local information, especially at low texture areas, resulting in poor geometry. To this end, we have taken steps to address this issue by introducing a structural regularization method to preserve local structural details. To evaluate the effectiveness of our approach, we establish an object-centric multi-view LiDAR dataset, dubbed NeRF-MVL. It contains observations of objects from 9 categories seen from 360-degree viewpoints captured with multiple LiDAR sensors. Our extensive experiments on the scene-level KITTI-360 dataset, and on our object-level NeRF-MVL show that our LiDAR-NeRF surpasses the model-based algorithms significantly.

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

By repository: official repository: 13 samples from 1 repository, 11 ran (8 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 between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tangtaogo/lidar-nerf officialmentioned on GitHubpytorchMITSyntology: 13 samples, 11 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

13 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 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.

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

Licence: 1 of the 13 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/lidar-nerf. “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/lidar-nerf official repository 13 samples, 11 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
filter_bbox_dataset lidarnerf/nerf/utils.py ran fingerprinted MIT (permissive) · ad1506ac834a0958 · report fixture: signature pc:ndarray/2/float, OBB_local:ndarray/2/float · returned ndarray · level recorded 2026-09-25
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) · a1cbcfad9b7fd40b · report fixture: signature local_points_with_intensities:ndarray/2/float, lidar_H:int/0/int, lidar_W:int/0/int, lidar_K:tuple/1/int, max_depth:int/0/int · returned tuple · level recorded 2026-09-24
linear_to_srgb in 9 papers lidarnerf/nerf/utils.py ran MIT (permissive) · df2164d2c1f74c1b · report fixture: returned Tensor · 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
sample_pdf in 37 papers lidarnerf/nerf/renderer.py ran · our draft was wrong MIT (permissive) · 8ed7b9fc7f33d1dd · report fixture: signature bins:Tensor/2/float, weights:Tensor/2/float, n_samples:int/0/int, det:bool/0/bool · returned Tensor · level recorded 2026-09-22
srgb_to_linear in 10 papers lidarnerf/nerf/utils.py ran MIT (permissive) · 78534c794e6d4ae8 · report fixture: returned Tensor · level recorded 2026-09-24
lidar_to_pano lidarnerf/convert.py unverified MIT (permissive) · 846c287e3db5197e · report
lidar_to_pano_with_intensities_with_bbox_mask lidarnerf/convert.py unverified MIT (permissive) · fcd40c17509b87bd · report

Tasks

3D ReconstructionNeRFNovel LiDAR View SynthesisNovel View SynthesisStyle Transfer

Datasets

Introduced by this paper, per the archive.

NeRF-MVL

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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