Papers › Loc-NeRF: Monte Carlo Localization using Neural Radiance Fields

Loc-NeRF: Monte Carlo Localization using Neural Radiance Fields

19 Sep 2022arXiv:2209.09050links table onlyarchive 2025-07-28

Dominic Maggio, Marcus Abate, Jingnan Shi, Courtney Mario, Luca Carlone

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

We present Loc-NeRF, a real-time vision-based robot localization approach that combines Monte Carlo localization and Neural Radiance Fields (NeRF). Our system uses a pre-trained NeRF model as the map of an environment and can localize itself in real-time using an RGB camera as the only exteroceptive sensor onboard the robot. While neural radiance fields have seen significant applications for visual rendering in computer vision and graphics, they have found limited use in robotics. Existing approaches for NeRF-based localization require both a good initial pose guess and significant computation, making them impractical for real-time robotics applications. By using Monte Carlo localization as a workhorse to estimate poses using a NeRF map model, Loc-NeRF is able to perform localization faster than the state of the art and without relying on an initial pose estimate. In addition to testing on synthetic data, we also run our system using real data collected by a Clearpath Jackal UGV and demonstrate for the first time the ability to perform real-time global localization with neural radiance fields. We make our code publicly available at https://github.com/MIT-SPARK/Loc-NeRF.

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

By repository: official repository: 9 samples from 1 repository, 7 ran (4 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. 1 of the 7 samples that ran has no recorded date.

mit-spark/loc-nerf officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 7 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

9 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 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 has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · our draft was wrong
4ran
2unverified

Licence: 1 of the 9 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 mit-spark/loc-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.

mit-spark/loc-nerf official repository 9 samples, 7 ran (3 instrument-failed) · 2 unverified
batchify in 71 papers
census: 6 implementations from 6 papers, 3 distinct outputs across 3 buckets, one shared input per bucket
src/full_nerf_helpers.py ran · our draft was wrong MIT (permissive) · fd57e365830d09de · report fixture: signature fn:callable/0/?, chunk:int/0/int · returned function · level recorded, date not recorded
get_embedder in 88 papers src/full_nerf_helpers.py ran · our draft was wrong fingerprinted MIT (permissive) · d26ffa77f1cd53a6 · report fixture: signature multires:int/0/int, i:int/0/int · returned tuple · level recorded 2026-09-22
get_pose src/utils.py ran MIT (permissive) · 60ed76adfd8aa0ea · report fixture: signature phi:float/0/float, theta:float/0/float, psi:float/0/float, x:float/0/float, y:float/0/float, z:float/0/float, obs_img_pose:ndarray/2/int, center_about_true_pose:bool/0/bool · returned ndarray · level recorded 2026-09-25
get_rays in 39 papers src/render_helpers.py ran MIT (permissive) · c03007b6cafd9690 · report fixture: signature H:int/0/int, W:int/0/int, focal:float/0/float, c2w:Tensor/2/float · returned tuple · level recorded 2026-09-25
get_rays_np in 13 papers src/render_helpers.py ran MIT (permissive) · 929e526ea6fc4975 · report fixture: signature H:int/0/int, W:int/0/int, focal:float/0/float, c2w:ndarray/2/float · returned tuple · level recorded 2026-09-25
ndc_rays in 12 papers src/render_helpers.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 4366d225ac2fe16d · report fixture: signature H:int/0/int, W:int/0/int, focal:float/0/float, near:float/0/float, rays_o:Tensor/2/float, rays_d:Tensor/2/float · returned tuple · level recorded 2026-09-22
rgb2bgr src/utils.py ran MIT (permissive) · 1f17e82449269b3b · report fixture: signature img_rgb:ndarray/3/int · returned ndarray · level recorded 2026-09-25
load_blender src/utils.py unverified MIT (permissive) · ec416c81cecb9865 · report
load_nerf src/full_nerf_helpers.py unverified MIT (permissive) · 01ae531174d0751c · report

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