Papers › CloudFixer: Test-Time Adaptation for 3D Point Clouds via Diffusion-Guided Geometric...
CloudFixer: Test-Time Adaptation for 3D Point Clouds via Diffusion-Guided Geometric Transformation
Hajin Shim, Changhun Kim, Eunho Yang
3D point clouds captured from real-world sensors frequently encompass noisy points due to various obstacles, such as occlusion, limited resolution, and variations in scale. These challenges hinder the deployment of pre-trained point cloud recognition models trained on clean point clouds, leading to significant performance degradation. While test-time adaptation (TTA) strategies have shown promising results on this issue in the 2D domain, their application to 3D point clouds remains under-explored. Among TTA methods, an input adaptation approach, which directly converts test instances to the source domain using a pre-trained diffusion model, has been proposed in the 2D domain. Despite its robust TTA performance in practical situations, naively adopting this into the 3D domain may be suboptimal due to the neglect of inherent properties of point clouds, and its prohibitive computational cost. Motivated by these limitations, we propose CloudFixer, a test-time input adaptation method tailored for 3D point clouds, employing a pre-trained diffusion model. Specifically, CloudFixer optimizes geometric transformation parameters with carefully designed objectives that leverage the geometric properties of point clouds. We also substantially improve computational efficiency by avoiding backpropagation through the diffusion model and a prohibitive generation process. Furthermore, we propose an online model adaptation strategy by aligning the original model prediction with that of the adapted input. Extensive experiments showcase the superiority of CloudFixer over various TTA baselines, excelling in handling common corruptions and natural distribution shifts across diverse real-world scenarios. Our code is available at https://github.com/shimazing/CloudFixer
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="2407.16193")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2407.16193", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2407.16193")
Code
Syntology 16 code samples harvested from 1 repository linked to this paper: 13 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 1 violated, 4 with no contract checked; 7 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 5 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: found in paper text by Syntology: 16 samples from 1 repository, 13 ran (6 with no instrument failure; 7 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. 1 of the 13 samples that ran has no recorded date.
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
16 samples harvested: 13 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 1 violated, 4 with no contract checked; 7 where Syntology's instrument failed) · 3 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.
Licence: 1 of the 16 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 shimazing/CloudFixer. “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.
df23da82fbd7ff7b · report
fixture: signature model:callable/0/? · returned int · level recorded 2026-09-24 census: 6 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 3, kind float, dtype float32 classifier/models.py ran; the contract check could not run (RAISES) MIT (permissive) ·
9a8756778dd8234a · report
fixture: returned Tensor · level recorded 2026-09-22 f00fffed990205f4 · report
fixture: signature args:Args/0/?, model:callable/0/?, ssl_loss:callable/0/? · returned AdamW · level recorded 2026-09-24 43510d2695421124 · report
fixture: signature model_str:str/0/str · returned type · level recorded 2026-09-24 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 classifier/models.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 dc21bf2cf5f7160d · report
fixture: signature pc:Tensor/3/float · returned Tensor · level recorded 2026-09-24 c3cb7594a2a0ff42 · report
fixture: signature batch:Tensor/3/float, label:str/0/str · returned tuple · level recorded 2026-09-24 f7c1ac6b75f91e49 · report
fixture: signature batch:Tensor/3/float, labels:Tensor/1/int · returned Tensor · level recorded 2026-09-24 a9abc40d045ad04c · report
fixture: signature batch_data:Tensor/3/float, rotation_angle:float/0/float · returned Tensor · level recorded 2026-09-24 census: 8 implementations from 9 papers, 7 distinct outputs across 5 buckets, one shared input per bucket train_dm.py ran MIT (permissive) ·
a82694d00afd7354 · report
fixture: signature args:Args/0/?, device:device/0/?, generative_model:callable/0/?, nodesxsample:Tensor/1/int, fix_noise:bool/0/bool · returned Tensor · level recorded 2026-09-24 census: 18 implementations from 29 papers, 4 distinct outputs across 2 buckets, one shared input per bucket utils/losses.py ran fingerprinted MIT (permissive) ·
6ae0cdec9fe5f43b · report
fixture: signature x:Tensor/2/float, dim:int/0/int · returned Tensor · level recorded 2026-09-24 7c508037b40522af · report
fixture: signature v:str/0/str · returned bool · level recorded, date not recorded census: 3 implementations from 5 papers, 3 distinct outputs across 3 buckets, one shared input per bucket utils/losses.py ran · our draft was wrong fingerprinted MIT (permissive) ·
90c529ca8e85d3db · report
fixture: signature x:Tensor/3/float · returned Tensor · level recorded 2026-09-24 b8c2aca158049aa6 · report
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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