Papers › Latent Noise Segmentation: How Neural Noise Leads to the Emergence of Segmentation and Grouping

Latent Noise Segmentation: How Neural Noise Leads to the Emergence of Segmentation and Grouping

28 Sep 2023arXiv:2309.16515archive 2025-07-28

Ben Lonnqvist, Zhengqing Wu, Michael H. Herzog

Humans are able to segment images effortlessly without supervision using perceptual grouping. Here, we propose a counter-intuitive computational approach to solving unsupervised perceptual grouping and segmentation: that they arise because of neural noise, rather than in spite of it. We (1) mathematically demonstrate that under realistic assumptions, neural noise can be used to separate objects from each other; (2) that adding noise in a DNN enables the network to segment images even though it was never trained on any segmentation labels; and (3) that segmenting objects using noise results in segmentation performance that aligns with the perceptual grouping phenomena observed in humans, and is sample-efficient. We introduce the Good Gestalt (GG) datasets -- six datasets designed to specifically test perceptual grouping, and show that our DNN models reproduce many important phenomena in human perception, such as illusory contours, closure, continuity, proximity, and occlusion. Finally, we (4) show that our model improves performance on our GG datasets compared to other tested unsupervised models by 24.9%. Together, our results suggest a novel unsupervised segmentation method requiring few assumptions, a new explanation for the formation of perceptual grouping, and a novel potential benefit of neural noise.

PaperPDFCodeCode Syntology ranMethod as code

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 13 code samples harvested from 1 repository linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 1 honoured, 1 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: 13 samples from 1 repository, 12 ran (11 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. 1 of the 12 samples that ran has no recorded date.

zhengqinguuu/latentnoisesegmentation officialmentioned in papermentioned on GitHubpytorchGPL-3.0Syntology: 13 samples, 12 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

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

Licence: 13 of the 13 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 zhengqinguuu/latentnoisesegmentation. “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.

zhengqinguuu/latentnoisesegmentation official repository 13 samples, 12 ran (1 instrument-failed) · 1 unverified
A_in_B umap_plotting.py ran GPL-3.0 (copyleft) · pointer only · 85f2fb693c3b6956 · report fixture: signature A:int/0/int, B:list/1/int · returned bool · level recorded 2026-09-24
cuda in 9 papers
census: 3 implementations from 7 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
utils.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted GPL-3.0 (copyleft) · pointer only · 8c252d04248affd7 · report fixture: signature tensor:Tensor/2/float, uses_cuda:bool/0/bool · returned Tensor · level recorded 2026-09-22
generate_Image_from_ndarray datasets/create_datasets.py ran GPL-3.0 (copyleft) · pointer only · 0eb2228302f0ca96 · report fixture: signature image:ndarray/3/int · returned Image · level recorded 2026-09-24
generate_possible_free_pixel_offset datasets/create_datasets.py ran fingerprinted GPL-3.0 (copyleft) · pointer only · 6b7d57e23335630d · report fixture: signature free_pixel_num:int/0/int · returned list · level recorded 2026-09-24
get_latest_version_folder utils.py ran fingerprinted GPL-3.0 (copyleft) · pointer only · f36b38e2b5d7683e · report fixture: signature training_outcome_savedir:str/0/str · returned str · level recorded 2026-09-24
kl_divergence in 86 papers
census: 18 implementations from 18 papers, 15 distinct outputs across 7 buckets, one shared input per bucket
solver.py ran fingerprinted GPL-3.0 (copyleft) · pointer only · 8e97dcc43326b0c1 · report fixture: signature mu:Tensor/2/float, logvar:Tensor/2/float · returned tuple · level recorded 2026-09-24
make_label_readable umap_plotting.py ran GPL-3.0 (copyleft) · pointer only · 1e726999714948ac · report fixture: signature dataset:str/0/str, input:str/0/str · returned str · level recorded 2026-09-24
reconstruction_loss in 14 papers solver.py ran fingerprinted GPL-3.0 (copyleft) · pointer only · 849bb2b9f4368182 · report fixture: signature x:Tensor/2/float, x_recon:Tensor/2/float · returned Tensor · level recorded 2026-09-24
reparametrize in 22 papers
census: 6 implementations from 8 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32
models.py ran · honoured contract fingerprinted GPL-3.0 (copyleft) · pointer only · 863fc64cd51264f0 · report fixture: signature mu:Tensor/2/float, logvar:Tensor/2/float · returned Tensor · level recorded 2026-09-22
return_color_hue_order_jpg umap_plotting.py ran GPL-3.0 (copyleft) · pointer only · f790e3af7b531d70 · report fixture: signature dataset:str/0/str · returned tuple · level recorded 2026-09-24
return_data in 6 papers dataloaders.py ran GPL-3.0 (copyleft) · pointer only · 75b9f9771c727b95 · report fixture: signature args:Args/0/?, return_testset:bool/0/bool · returned list · level recorded 2026-09-24
str2bool in 533 papers utils.py ran · violated contract GPL-3.0 (copyleft) · pointer only · f017532fc389cbfe · report fixture: signature v:str/0/str · returned bool · level recorded, date not recorded
NoisySegmentation segmentation.py unverified GPL-3.0 (copyleft) · pointer only · d182c62fb46c1bb1 · 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 Latent Noise Segmentation (graph method: Latent Noise Segmentation). 1 brick; individually on a fixture: 0 ran · 1 unverified. The assembly has not been run end-to-end.

  1. NoisySegmentation entry · level 0 · unverified · d182c62fb46c1bb1

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="2309.16515") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

SegmentationSemantic Segmentation

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