Papers › OpenScene: 3D Scene Understanding with Open Vocabularies

OpenScene: 3D Scene Understanding with Open Vocabularies

28 Nov 2022CVPR 2023 1arXiv:2211.15654archive 2025-07-28

Songyou Peng, Kyle Genova, Chiyu "Max" Jiang, Andrea Tagliasacchi, Marc Pollefeys, Thomas Funkhouser

Traditional 3D scene understanding approaches rely on labeled 3D datasets to train a model for a single task with supervision. We propose OpenScene, an alternative approach where a model predicts dense features for 3D scene points that are co-embedded with text and image pixels in CLIP feature space. This zero-shot approach enables task-agnostic training and open-vocabulary queries. For example, to perform SOTA zero-shot 3D semantic segmentation it first infers CLIP features for every 3D point and later classifies them based on similarities to embeddings of arbitrary class labels. More interestingly, it enables a suite of open-vocabulary scene understanding applications that have never been done before. For example, it allows a user to enter an arbitrary text query and then see a heat map indicating which parts of a scene match. Our approach is effective at identifying objects, materials, affordances, activities, and room types in complex 3D scenes, all using a single model trained without any labeled 3D data.

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

pengsongyou/openscene mentioned on GitHubpytorchApache-2.0Syntology: 9 samples, 7 ran (5 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; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 5 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 · honoured contract
4ran · our draft was wrong
1ran; the contract check could not run
2unverified

Licence: 8 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. For 8 of them, 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 pengsongyou/openscene. “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.

pengsongyou/openscene community (archive-listed) 9 samples, 7 ran (5 instrument-failed) · 2 unverified
M in 10 papers dataset/voxelizer.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) · 3095f89bf0fc823d · report fixture: signature axis:ndarray/1/float, theta:float/0/float · returned ndarray · level recorded 2026-09-25
collation_fn dataset/feature_loader.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · f726974066cf1352 · report fixture: signature batch:list/1/tuple · returned tuple · level recorded 2026-09-24
collation_fn_eval_all dataset/feature_loader.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · 65392c9cae62b77b · report fixture: signature batch:list/1/tuple · returned tuple · level recorded 2026-09-24
collation_fn_eval_all dataset/point_loader.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · cc9a3557465a7813 · report fixture: signature batch:list/1/tuple · returned tuple · level recorded 2026-09-24
fnv_hash_vec in 14 papers dataset/voxelization_utils.py ran · honoured contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 0086c892bd1df796 · report fixture: signature arr:ndarray/2/int · returned ndarray · level recorded 2026-09-25
ravel_hash_vec in 13 papers dataset/voxelization_utils.py ran · honoured contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · afdc8ad15d9098b8 · report fixture: signature arr:ndarray/2/int · returned ndarray · level recorded 2026-09-25
state_dict_remove_moudle models/disnet.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · c4b88bc6388a332e · report fixture: signature state_dict:dict/0/? · returned OrderedDict · level recorded 2026-09-24
collation_fn dataset/point_loader.py unverified Apache-2.0 (permissive) here; the stored copy is pointer only · bc5616d55b1b06b2 · report
get_release_scans dataset/scannet/download-scannet.py unverified Apache-2.0 (permissive) here; the stored copy is pointer only · 5905d8e45b03578e · report

Tasks

3D Open-Vocabulary Instance Segmentation3D Semantic SegmentationScene UnderstandingSemantic Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Open-Vocabulary Instance Segmentation Replica OpenScene + Mask3D mAP 10.9 #7 of 7 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

CLIP

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