Papers › Domain Adaptation on Point Clouds via Geometry-Aware Implicits

Domain Adaptation on Point Clouds via Geometry-Aware Implicits

17 Dec 2021CVPR 2022 1arXiv:2112.09343archive 2025-07-28

Yuefan Shen, Yanchao Yang, Mi Yan, He Wang, Youyi Zheng, Leonidas Guibas

As a popular geometric representation, point clouds have attracted much attention in 3D vision, leading to many applications in autonomous driving and robotics. One important yet unsolved issue for learning on point cloud is that point clouds of the same object can have significant geometric variations if generated using different procedures or captured using different sensors. These inconsistencies induce domain gaps such that neural networks trained on one domain may fail to generalize on others. A typical technique to reduce the domain gap is to perform adversarial training so that point clouds in the feature space can align. However, adversarial training is easy to fall into degenerated local minima, resulting in negative adaptation gains. Here we propose a simple yet effective method for unsupervised domain adaptation on point clouds by employing a self-supervised task of learning geometry-aware implicits, which plays two critical roles in one shot. First, the geometric information in the point clouds is preserved through the implicit representations for downstream tasks. More importantly, the domain-specific variations can be effectively learned away in the implicit space. We also propose an adaptive strategy to compute unsigned distance fields for arbitrary point clouds due to the lack of shape models in practice. When combined with a task loss, the proposed outperforms state-of-the-art unsupervised domain adaptation methods that rely on adversarial domain alignment and more complicated self-supervised tasks. Our method is evaluated on both PointDA-10 and GraspNet datasets. The code and trained models will be publicly available.

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: 8 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 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, 8 ran (6 with no instrument failure; 2 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.

Jhonve/jhonve.github.io mentioned on GitHubApache-2.0Syntology: not harvested report
jhonve/implicitpcda mentioned on GitHubpytorchMITSyntology: 9 samples, 8 ran (2 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

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

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

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

jhonve/implicitpcda community (archive-listed) 9 samples, 8 ran (2 instrument-failed) · 1 unverified
datapath_PointDAN_synthetic datasets/datautils.py ran MIT (permissive) · 343cae110d7d50b0 · report fixture: signature datapath:str/0/str, folder_list:list/1/str, is_train:bool/0/bool · returned list · level recorded 2026-09-24
get_scheduler in 122 papers models/networks.py ran MIT (permissive) here; the stored copy is pointer only · f28f371ac79d4e8a · report fixture: signature optimizer:Adam/0/?, opt:Options/0/? · returned LambdaLR · level recorded 2026-09-24
init_net in 47 papers models/networks.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 01d1ccc6bbadcbdc · report fixture: signature net:callable/0/?, init_type:str/0/str, init_gain:float/0/float, gpu_ids:list/1/empty, debug:bool/0/bool, initialize_weights:bool/0/bool · returned SimpleNet · level recorded 2026-09-22
js_divergence in 12 papers measurement/calculate_distances.py ran fingerprinted MIT (permissive) · 6cd4ea67bd085b10 · report fixture: signature p_output:Tensor/2/float, q_output:Tensor/2/float, get_softmax:bool/0/bool · returned Tensor · level recorded 2026-09-24
knn in 87 papers
census: 12 implementations from 17 papers, 6 distinct outputs across 4 buckets, one shared input per bucket this sample: bucket 1 of 4, arg 1: rank 3, kind float, dtype float32
models/networks.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · cdd0141594039dcb · report fixture: signature x:Tensor/3/float, k:int/0/int · returned Tensor · level recorded 2026-09-22
mmd_linear measurement/mmd_numpy_scipy.py ran fingerprinted MIT (permissive) · 67b50915ffecdc32 · report fixture: signature X:ndarray/2/float, Y:ndarray/2/float · returned float32 · level recorded 2026-09-24
mmd_poly measurement/mmd_numpy_scipy.py ran MIT (permissive) · c2d3ab5d43b0c7dc · report fixture: signature X:ndarray/2/float, Y:ndarray/2/float, degree:int/0/int, gamma:int/0/int, coef0:int/0/int · returned float64 · level recorded 2026-09-24
mmd_rbf in 6 papers measurement/mmd_numpy_scipy.py ran fingerprinted MIT (permissive) · af690a6cc7e92c9f · report fixture: signature X:ndarray/2/float, Y:ndarray/2/float, gamma:float/0/float · returned float64 · level recorded 2026-09-24
convert_model in 14 papers models/sync_batchnorm/batchnorm.py unverified MIT (permissive) · fd571474b78c67d9 · report

Tasks

Autonomous DrivingDomain AdaptationUnsupervised Domain Adaptation

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