Papers › OV-NeRF: Open-vocabulary Neural Radiance Fields with Vision and Language Foundation...

OV-NeRF: Open-vocabulary Neural Radiance Fields with Vision and Language Foundation Models for 3D Semantic Understanding

7 Feb 2024arXiv:2402.04648archive 2025-07-28

Guibiao Liao, Kaichen Zhou, Zhenyu Bao, Kanglin Liu, Qing Li

The development of Neural Radiance Fields (NeRFs) has provided a potent representation for encapsulating the geometric and appearance characteristics of 3D scenes. Enhancing the capabilities of NeRFs in open-vocabulary 3D semantic perception tasks has been a recent focus. However, current methods that extract semantics directly from Contrastive Language-Image Pretraining (CLIP) for semantic field learning encounter difficulties due to noisy and view-inconsistent semantics provided by CLIP. To tackle these limitations, we propose OV-NeRF, which exploits the potential of pre-trained vision and language foundation models to enhance semantic field learning through proposed single-view and cross-view strategies. First, from the single-view perspective, we introduce Region Semantic Ranking (RSR) regularization by leveraging 2D mask proposals derived from Segment Anything (SAM) to rectify the noisy semantics of each training view, facilitating accurate semantic field learning. Second, from the cross-view perspective, we propose a Cross-view Self-enhancement (CSE) strategy to address the challenge raised by view-inconsistent semantics. Rather than invariably utilizing the 2D inconsistent semantics from CLIP, CSE leverages the 3D consistent semantics generated from the well-trained semantic field itself for semantic field training, aiming to reduce ambiguity and enhance overall semantic consistency across different views. Extensive experiments validate our OV-NeRF outperforms current state-of-the-art methods, achieving a significant improvement of 20.31% and 18.42% in mIoU metric on Replica and ScanNet, respectively. Furthermore, our approach exhibits consistent superior results across various CLIP configurations, further verifying its robustness. Project page: https://github.com/pcl3dv/OV-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 13 code samples harvested from 1 repository linked to this paper: 12 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; 8 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; 4 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, 12 ran (4 with no instrument failure; 8 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.

pcl3dv/ov-nerf officialmentioned in papermentioned on GitHubpytorchSyntology: 13 samples, 12 ran (8 instrument-failed) · 1 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: 12 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; 8 where Syntology's instrument failed) · 1 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.

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

Licence: 13 of the 13 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 pcl3dv/ov-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.

pcl3dv/ov-nerf official repository 13 samples, 12 ran (8 instrument-failed) · 1 unverified
OctreeRender_trilinear_fast in 11 papers renderer.py ran no licence file found · pointer only · 945933374c5e3cbf · report fixture: signature rays:Tensor/2/float, tensorf:callable/0/?, chunk:int/0/int, N_samples:int/0/int, ndc_ray:bool/0/bool, white_bg:bool/0/bool, is_train:bool/0/bool, render_feature:bool/0/bool, out_rgb:bool/0/bool, device:str/0/str · returned tuple · level recorded 2026-09-24
OctreeRender_trilinear_fast_depth renderer.py ran no licence file found · pointer only · eae018b803b70a00 · report fixture: signature rays:Tensor/2/float, tensorf:callable/0/?, chunk:int/0/int, N_samples:int/0/int, ndc_ray:bool/0/bool, is_train:bool/0/bool, device:str/0/str · returned Tensor · level recorded 2026-09-24
circle in 7 papers dataLoader/scannet.py ran no licence file found · pointer only · da07cd5065ff06f6 · report fixture: signature radius:float/0/float, h:float/0/float, axis:str/0/str, t0:int/0/int, r:int/0/int · returned function · level recorded 2026-09-24
cross in 9 papers dataLoader/scannet.py ran fingerprinted no licence file found · pointer only · bc9608bb992f2402 · report fixture: signature x:Tensor/2/float, y:Tensor/2/float, axis:int/0/int · returned Tensor · level recorded 2026-09-24
eval_sh in 22 papers models/sh.py ran; the contract check could not run (RAISES) no licence file found · pointer only · db95ecdf5d4abe6b · report fixture: signature deg:int/0/int, sh:Tensor/3/float, dirs:Tensor/2/float · returned Tensor · level recorded 2026-09-24
eval_sh_bases in 17 papers models/sh.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · caa9e209a9083a0f · report fixture: signature deg:int/0/int, dirs:Tensor/2/float · returned Tensor · level recorded 2026-09-22
get_json_content dataLoader/scannet.py ran · our draft was wrong no licence file found · pointer only · ee7f22f35fc91bae · report fixture: signature path:str/0/str · returned dict · level recorded 2026-09-24
init_log in 16 papers funcs.py ran · our draft was wrong no licence file found · pointer only · dc510fe4f2261490 · report fixture: signature log:dict/0/?, keys:list/1/str · returned dict · level recorded 2026-09-24
positional_encoding in 63 papers
census: 5 implementations from 6 papers, 4 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/tensorBase.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 11a10efa60767162 · report fixture: signature positions:Tensor/2/float, freqs:int/0/int · returned Tensor · level recorded 2026-09-22
raw2alpha in 17 papers models/tensorBase.py ran · our draft was wrong fingerprinted no licence file found · pointer only · c1acffa981204fee · report fixture: signature sigma:Tensor/2/float, dist:Tensor/2/float · returned tuple · level recorded 2026-09-24
visualize_depth in 16 papers funcs.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 5346431312bff754 · report fixture: signature depth:Tensor/2/float, minmax:NoneType/0/?, cmap:int/0/int · returned tuple · level recorded 2026-09-24
visualize_depth_numpy in 14 papers funcs.py ran; the contract check could not run (RAISES) no licence file found · pointer only · c775698c33cfa2de · report fixture: signature depth:ndarray/2/float, minmax:NoneType/0/?, cmap:int/0/int · returned tuple · level recorded 2026-09-24
SHRender in 11 papers models/tensorBase.py unverified no licence file found · pointer only · 3a530f556e40d9c0 · report

Tasks

NeRF

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

CLIPSAM

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