Papers › OGC: Unsupervised 3D Object Segmentation from Rigid Dynamics of Point Clouds
OGC: Unsupervised 3D Object Segmentation from Rigid Dynamics of Point Clouds
Ziyang Song, Bo Yang
In this paper, we study the problem of 3D object segmentation from raw point clouds. Unlike all existing methods which usually require a large amount of human annotations for full supervision, we propose the first unsupervised method, called OGC, to simultaneously identify multiple 3D objects in a single forward pass, without needing any type of human annotations. The key to our approach is to fully leverage the dynamic motion patterns over sequential point clouds as supervision signals to automatically discover rigid objects. Our method consists of three major components, 1) the object segmentation network to directly estimate multi-object masks from a single point cloud frame, 2) the auxiliary self-supervised scene flow estimator, and 3) our core object geometry consistency component. By carefully designing a series of loss functions, we effectively take into account the multi-object rigid consistency and the object shape invariance in both temporal and spatial scales. This allows our method to truly discover the object geometry even in the absence of annotations. We extensively evaluate our method on five datasets, demonstrating the superior performance for object part instance segmentation and general object segmentation in both indoor and the challenging outdoor scenarios.
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):
get_harvested_code_for_paper(arxiv_id="2210.04458")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2210.04458", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2210.04458")
Code
Syntology 20 code samples harvested from 1 repository linked to this paper: 13 ran (of which 9 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 1 where Syntology's instrument failed) · 7 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 20 samples from 1 repository, 13 ran (12 with no instrument failure; 1 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.
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
20 samples harvested: 13 ran (of which 9 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 1 where Syntology's instrument failed) · 7 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.
Licence: 20 of the 20 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 vlar-group/ogc. “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”. For 4 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.
7d9e410588d38e38 · report
fixture: returned BatchNorm1d · level recorded 2026-09-22 ea90589983c7d4fb · report
fixture: returned BatchNorm2d · level recorded 2026-09-22 census: 7 implementations from 7 papers, 6 distinct outputs on one shared input models/segnet_ogcdr.py ran · metamorphic tier: deterministic fingerprinted licence not identified · pointer only ·
66590da846c5ae6d · report
fixture: returned Conv2d · level recorded 2026-09-22 d14c0948cfdb965a · report
fixture: signature input:Tensor/2/float · returned Tensor · level recorded 2026-09-24 a005fafa886ca6c7 · report
fixture: returned GroupNorm · level recorded 2026-09-22 20e3a97f6963192c · report
fixture: returned MaskFormerHead · level recorded 2026-09-22 3d9e9e52517e5797 · report
fixture: returned Seq · level recorded 2026-09-22 f38f770e896d67f3 · report
fixture: returned SharedMLP · level recorded 2026-09-22 19e06e5da5917030 · report
fixture: signature slot:Tensor/3/float, point_feats:Tensor/3/float, pos_enc:Tensor/3/float · returned Tensor · level recorded 2026-09-24 359fcb0c4f682234 · report
fixture: returned _BNBase · level recorded 2026-09-22 6cec49255b1f095e · report
fixture: signature input:Tensor/4/float · returned Tensor · level recorded 2026-09-24 6597c3e0acab9f29 · report
fixture: returned _PointnetSAModuleBase · level recorded 2026-09-22 c1467b825cc365c5 · report
fixture: signature layer_def:dict/0/?, dimension:int/0/int · returned GroupNorm · level recorded 2026-09-22 815a433370418f73 · report
5d260efae3a9b405 · report
5e62857933c0d4e6 · report
2336b94be0832500 · report
af2fc6415208e147 · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.
1 assembly on this paper: 1 harvested, 0 generated.
harvested Assembly for OGC (graph method: OGC). 18 bricks; individually on a fixture: 13 ran (of which 9 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 1 where Syntology's instrument failed) · 5 unverified. The assembly has not been run end-to-end.
- MaskFormer3D entry · level 0 · unverified ·
5d260efae3a9b405 - MaskFormerHead helper · level 1 · ran ·
20e3a97f6963192c - PointnetFPModule helper · level 0 · unverified ·
5e62857933c0d4e6 - PointnetSAModule helper · level 0 · unverified ·
2336b94be0832500 - PointnetSAModuleMSG helper · level 0 · unverified ·
af2fc6415208e147 - Seq helper · level 1 · ran ·
3d9e9e52517e5797 - TransformerDecoderLayer helper · level 1 · ran ·
19e06e5da5917030 - SharedMLP helper · level 1 · ran ·
f38f770e896d67f3 - _PointnetSAModuleBase helper · level 1 · ran ·
6597c3e0acab9f29 - Conv1d helper · level 0 · unverified ·
815a433370418f73 - Conv2d helper · level 1 · ran ·
66590da846c5ae6d - FC helper · level 1 · ran ·
d14c0948cfdb965a - _ConvBase helper · level 1 · ran ·
6cec49255b1f095e - get_norm_layer helper · level 1 · ran · our draft was wrong ·
c1467b825cc365c5 - BatchNorm1d helper · level 1 · ran ·
7d9e410588d38e38 - BatchNorm2d helper · level 1 · ran ·
ea90589983c7d4fb - GroupNorm helper · level 1 · ran ·
a005fafa886ca6c7 - _BNBase helper · level 1 · ran ·
359fcb0c4f682234
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2210.04458") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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