Methods › General › Clustering › FINCH

First Integer Neighbor Clustering Hierarchy

FINCH

10 papers tagged archive 2025-07-28

Introduced by Saquib Sarfraz et al. in Efficient Parameter-Free Clustering Using First Neighbor Relations

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

The archive carries only a placeholder description for this method.

PaperSource

In Syntology repository known, no verified implementation (declared_code; repositories: 1 listed of 1 in the graph, strongest link: listed only). The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:2605.20005) is about this method is not checked.

Origin paper of this answer, arXiv:2605.20005 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified (of 1 harvested sample) · 1 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

Papers archive 2025-07-28

archive papers tagged: 10 · with a code link: 6 · where Syntology ran a sample: 2 (2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (2 of 10 tagged: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 10 of 10, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

18 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Contrastive Learning2
Language Modeling2
Language Modelling2
Large Language Model2
Action Detection1
Activity Detection1
Clustering1
Denoising1
Dialogue Evaluation1
Federated Learning1
GPU1
Hyperspectral Image Denoising1
Image Denoising1
Mamba1
Retrieval-augmented Generation1
Sound Classification1
Speaker Verification1
Transfer Learning1

Usage over time archive 2025-07-28

Papers per year tagged with FINCH: 2019 to 2025, peak 6 6 0 2019: 1 paper 2019 2020: 0 papers 2020 2021: 1 paper 2021 2022: 0 papers 2022 2023: 0 papers 2023 2024: 6 papers 2024 2025: 2 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (10 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Clustering

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