Papers › WeatherGen: A Unified Diverse Weather Generator for LiDAR Point Clouds via Spider...

WeatherGen: A Unified Diverse Weather Generator for LiDAR Point Clouds via Spider Mamba Diffusion

18 Apr 2025CVPR 2025 1arXiv:2504.13561archive 2025-07-28

Yang Wu, Yun Zhu, Kaihua Zhang, Jianjun Qian, Jin Xie, Jian Yang

3D scene perception demands a large amount of adverse-weather LiDAR data, yet the cost of LiDAR data collection presents a significant scaling-up challenge. To this end, a series of LiDAR simulators have been proposed. Yet, they can only simulate a single adverse weather with a single physical model, and the fidelity of the generated data is quite limited. This paper presents WeatherGen, the first unified diverse-weather LiDAR data diffusion generation framework, significantly improving fidelity. Specifically, we first design a map-based data producer, which can provide a vast amount of high-quality diverse-weather data for training purposes. Then, we utilize the diffusion-denoising paradigm to construct a diffusion model. Among them, we propose a spider mamba generator to restore the disturbed diverse weather data gradually. The spider mamba models the feature interactions by scanning the LiDAR beam circle or central ray, excellently maintaining the physical structure of the LiDAR data. Subsequently, following the generator to transfer real-world knowledge, we design a latent feature aligner. Afterward, we devise a contrastive learning-based controller, which equips weather control signals with compact semantic knowledge through language supervision, guiding the diffusion model to generate more discriminative data. Extensive evaluations demonstrate the high generation quality of WeatherGen. Through WeatherGen, we construct the mini-weather dataset, promoting the performance of the downstream task under adverse weather conditions. Code is available: https://github.com/wuyang98/weathergen

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 11 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 10 ran (9 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

wuyang98/weathergen officialmentioned in paperpytorchMITSyntology: 11 samples, 10 ran (1 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

11 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 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; the contract check could not run
9ran
1unverified

Licence: 0 of the 11 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 wuyang98/weathergen. “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.

wuyang98/weathergen official repository 11 samples, 10 ran (1 instrument-failed) · 1 unverified
cdist_rbf metrics/bev.py ran fingerprinted MIT (permissive) · 8786933bc5aae78d · report fixture: signature p:Tensor/2/float, q:Tensor/2/float, sigma:float/0/float · returned Tensor · level recorded 2026-09-24
components_from_spherical_harmonics models/encoding.py ran fingerprinted MIT (permissive) · 07fc468c17c6e3d4 · report fixture: signature levels:int/0/int, directions:Tensor/3/float · returned Tensor · level recorded 2026-09-24
compute_frechet_distance in 7 papers metrics/distribution.py ran fingerprinted MIT (permissive) · d671e8485cbec728 · report fixture: signature feats1:ndarray/2/float, feats2:ndarray/2/float · returned float · level recorded 2026-09-24
compute_jsd_2d metrics/bev.py ran MIT (permissive) · 4a22c88c27ba8887 · report fixture: signature hist1:Tensor/3/float, hist2:Tensor/3/float · returned float32 · level recorded 2026-09-24
compute_squared_mmd metrics/distribution.py ran MIT (permissive) · 7461447a581621e6 · report fixture: signature feats1:ndarray/2/float, feats2:ndarray/2/float, num_subsets:int/0/int, max_subset_size:int/0/int · returned float · level recorded 2026-09-24
generate_polar_coords models/encoding.py ran MIT (permissive) · 2e678e95ef0c4dd1 · report fixture: signature H:int/0/int, W:int/0/int, device:device/0/? · returned Tensor · level recorded 2026-09-24
get_hdl64e_linear_ray_angles evaluate_weather.py ran MIT (permissive) · e0e80565163c44db · report fixture: signature HH:int/0/int, WW:int/0/int, device:device/0/? · returned Tensor · level recorded 2026-09-24
point_cloud_to_histogram metrics/bev.py ran MIT (permissive) · dd28dc16f21bab45 · report fixture: signature point_cloud:Tensor/2/float, field_size:float/0/float, bins:int/0/int, min_depth:float/0/float, max_depth:float/0/float · returned Tensor · level recorded 2026-09-24
resize in 108 papers
census: 10 implementations from 14 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 4, kind float, dtype float32
evaluate.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) · 8907b6307e2f248b · report fixture: signature x:Tensor/4/float, size:tuple/1/int · returned Tensor · level recorded 2026-09-22
scatter in 33 papers evaluate_weather.py ran MIT (permissive) · 5dded98cc63dcf0c · report fixture: signature array:ndarray/2/float, index:list/1/tuple, value:list/1/float · returned ndarray · level recorded 2026-09-25

Tasks

Contrastive LearningDenoisingMambaWorld Knowledge

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

DiffusionMamba

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