Papers › N2D: (Not Too) Deep Clustering via Clustering the Local Manifold of an Autoencoded Embedding

N2D: (Not Too) Deep Clustering via Clustering the Local Manifold of an Autoencoded Embedding

16 Aug 2019arXiv:1908.05968archive 2025-07-28

Ryan McConville, Raul Santos-Rodriguez, Robert J. Piechocki, Ian Craddock

Deep clustering has increasingly been demonstrating superiority over conventional shallow clustering algorithms. Deep clustering algorithms usually combine representation learning with deep neural networks to achieve this performance, typically optimizing a clustering and non-clustering loss. In such cases, an autoencoder is typically connected with a clustering network, and the final clustering is jointly learned by both the autoencoder and clustering network. Instead, we propose to learn an autoencoded embedding and then search this further for the underlying manifold. For simplicity, we then cluster this with a shallow clustering algorithm, rather than a deeper network. We study a number of local and global manifold learning methods on both the raw data and autoencoded embedding, concluding that UMAP in our framework is best able to find the most clusterable manifold in the embedding, suggesting local manifold learning on an autoencoded embedding is effective for discovering higher quality discovering clusters. We quantitatively show across a range of image and time-series datasets that our method has competitive performance against the latest deep clustering algorithms, including out-performing current state-of-the-art on several. We postulate that these results show a promising research direction for deep clustering. The code can be found at https://github.com/rymc/n2d

PaperPDFCodeCode 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 4 code samples harvested from 2 repositories linked to this paper: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 2 samples from 1 repository, 2 ran (0 with no instrument failure; 2 where Syntology's instrument failed); community (archive-listed): 2 samples from 1 repository, 0 ran (0 with no instrument failure; 0 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

rymc/n2d officialmentioned in papermentioned on GitHubtfSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
josephsdavid/N2D mentioned on GitHubtfSyntology: 2 samples, 0 ran · 2 unverified report
shyhyawJou/N2D-Pytorch mentioned on GitHubpytorchGPL-3.0Syntology: not harvested report
talwiener/ds_hw3 mentioned on GitHubtfGPL-3.0Syntology: not harvested report
talwiener/n2d mentioned on GitHubtfSyntology: not harvested 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

4 samples harvested: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

2ran · our draft was wrong
2unverified

Licence: 2 of the 4 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

rymc/n2d official repository 2 samples, 2 ran (2 instrument-failed) · 0 unverified
load_pendigits datasets.py ran · our draft was wrong GPL-3.0 (copyleft) · pointer only · 29b317a560e0783f · report fixture: signature data_path:str/0/str · returned tuple · level recorded 2026-09-22
load_usps datasets.py ran · our draft was wrong GPL-3.0 (copyleft) · pointer only · dcfc17065b8e6966 · report fixture: signature data_path:str/0/str · returned tuple · level recorded 2026-09-22
josephsdavid/N2D community (archive-listed) 2 samples, 0 ran · 2 unverified
best_cluster_fit n2d/N2D.py unverified MIT (permissive) · 59c55deb36829817 · report
cluster_acc in 33 papers n2d/N2D.py unverified MIT (permissive) · 4efdad7e624a3c0d · report

Tasks

ClusteringDeep ClusteringImage ClusteringRepresentation LearningTime SeriesTime Series AnalysisTime Series Clustering

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Clustering Fashion-MNIST N2D (UMAP) Accuracy 0.672 #4 of 13 Archive leaderboard report
Image Clustering Fashion-MNIST N2D (UMAP) NMI 0.684 #4 of 13 Archive leaderboard report
Image Clustering HAR N2D (UMAP) Accuracy 0.801 #2 of 3 Archive leaderboard report
Image Clustering HAR N2D (UMAP) NMI 0.683 #2 of 3 Archive leaderboard report
Image Clustering MNIST-full N2D (UMAP) Accuracy 0.987 #3 of 16 Archive leaderboard report
Image Clustering MNIST-full N2D (UMAP) NMI 0.964 #3 of 16 Archive leaderboard report
Image Clustering MNIST-test N2D (UMAP) Accuracy 0.948 #9 of 11 Archive leaderboard report
Image Clustering MNIST-test N2D (UMAP) NMI 0.882 #9 of 11 Archive leaderboard report
Image Clustering USPS N2D (UMAP) Accuracy 0.958 #10 of 16 Archive leaderboard report
Image Clustering USPS N2D (UMAP) NMI 0.901 #10 of 16 Archive leaderboard report
Image Clustering pendigits N2D (UMAP) Accuracy 0.885 #1 of 2 Archive leaderboard report
Image Clustering pendigits N2D (UMAP) NMI 0.863 #1 of 2 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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