Papers › Self-Supervised Transformers for Unsupervised Object Discovery using Normalized Cut

Self-Supervised Transformers for Unsupervised Object Discovery using Normalized Cut

23 Feb 2022CVPR 2022 1arXiv:2202.11539archive 2025-07-28

Yangtao Wang, Xi Shen, Shell Hu, Yuan Yuan, James Crowley, Dominique Vaufreydaz

Transformers trained with self-supervised learning using self-distillation loss (DINO) have been shown to produce attention maps that highlight salient foreground objects. In this paper, we demonstrate a graph-based approach that uses the self-supervised transformer features to discover an object from an image. Visual tokens are viewed as nodes in a weighted graph with edges representing a connectivity score based on the similarity of tokens. Foreground objects can then be segmented using a normalized graph-cut to group self-similar regions. We solve the graph-cut problem using spectral clustering with generalized eigen-decomposition and show that the second smallest eigenvector provides a cutting solution since its absolute value indicates the likelihood that a token belongs to a foreground object. Despite its simplicity, this approach significantly boosts the performance of unsupervised object discovery: we improve over the recent state of the art LOST by a margin of 6.9%, 8.1%, and 8.1% respectively on the VOC07, VOC12, and COCO20K. The performance can be further improved by adding a second stage class-agnostic detector (CAD). Our proposed method can be easily extended to unsupervised saliency detection and weakly supervised object detection. For unsupervised saliency detection, we improve IoU for 4.9%, 5.2%, 12.9% on ECSSD, DUTS, DUT-OMRON respectively compared to previous state of the art. For weakly supervised object detection, we achieve competitive performance on CUB and ImageNet.

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 1 code sample harvested from 1 repository linked to this paper: 1 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; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; 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: community (archive-listed): 1 sample from 1 repository, 1 ran (0 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

YangtaoWANG95/TokenCut mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 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

1 sample harvested: 1 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; 1 where Syntology's instrument failed) · 0 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.

1ran; the contract check could not run

Licence: 0 of the 1 sample 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 YangtaoWANG95/TokenCut. “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.

YangtaoWANG95/TokenCut community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
mask_color_compose unsupervised_saliency_detection/get_saliency.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) · 9eb48bfcce51ff49 · report fixture: signature org:ndarray/3/int, mask:ndarray/2/float, mask_color:list/1/int · returned Image · level recorded 2026-09-22

Tasks

ObjectObject DetectionObject DiscoverySaliency DetectionSingle-object discoveryUnsupervised Saliency DetectionWeakly Supervised Object DetectionWeakly-Supervised Object Localizationobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Single-object discovery COCO_20k TokenCut + CAD CorLoc 62.6 #4 of 10 Archive leaderboard report
Single-object discovery COCO_20k TokenCut CorLoc 58.8 #5 of 10 Archive leaderboard report
Unsupervised Saliency Detection DUT-OMRON TokenCut Accuracy 89.7 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection DUT-OMRON TokenCut IoU 61.8 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection DUT-OMRON TokenCut maximal F-measure 69.7 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection DUTS TokenCut Accuracy 91.4 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection DUTS TokenCut IoU 62.4 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection DUTS TokenCut maximal F-measure 75.5 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection ECSSD TokenCut Accuracy 93.4 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection ECSSD TokenCut IoU 77.2 #3 of 3 Archive leaderboard report
Unsupervised Saliency Detection ECSSD TokenCut maximal F-measure 87.4 #3 of 3 Archive leaderboard report
Weakly-Supervised Object Localization CUB TokenCut Top-1 Localization Accuracy 72.9 #1 of 1 Archive leaderboard report
Weakly-Supervised Object Localization CUB-200-2011 TokenCut Top-1 Localization Accuracy 72.9 #7 of 10 Archive leaderboard report
Weakly-Supervised Object Localization ImageNet TokenCut GT-known localization accuracy 65.4 #4 of 6 Archive leaderboard report
Weakly-Supervised Object Localization ImageNet TokenCut Top-1 Localization Accuracy 52.3 #4 of 6 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.

Methods

Spectral 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