Papers › Learning Semi-supervised Gaussian Mixture Models for Generalized Category Discovery

Learning Semi-supervised Gaussian Mixture Models for Generalized Category Discovery

10 May 2023ICCV 2023 1arXiv:2305.06144archive 2025-07-28

Bingchen Zhao, Xin Wen, Kai Han

In this paper, we address the problem of generalized category discovery (GCD), i.e., given a set of images where part of them are labelled and the rest are not, the task is to automatically cluster the images in the unlabelled data, leveraging the information from the labelled data, while the unlabelled data contain images from the labelled classes and also new ones. GCD is similar to semi-supervised learning (SSL) but is more realistic and challenging, as SSL assumes all the unlabelled images are from the same classes as the labelled ones. We also do not assume the class number in the unlabelled data is known a-priori, making the GCD problem even harder. To tackle the problem of GCD without knowing the class number, we propose an EM-like framework that alternates between representation learning and class number estimation. We propose a semi-supervised variant of the Gaussian Mixture Model (GMM) with a stochastic splitting and merging mechanism to dynamically determine the prototypes by examining the cluster compactness and separability. With these prototypes, we leverage prototypical contrastive learning for representation learning on the partially labelled data subject to the constraints imposed by the labelled data. Our framework alternates between these two steps until convergence. The cluster assignment for an unlabelled instance can then be retrieved by identifying its nearest prototype. We comprehensively evaluate our framework on both generic image classification datasets and challenging fine-grained object recognition datasets, achieving state-of-the-art performance.

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: 9 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 3 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, 9 ran (4 with no instrument failure; 5 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-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 9 samples that ran have no recorded date.

DTennant/GPC officialpytorchMITSyntology: 11 samples, 9 ran (5 instrument-failed) · 2 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: 9 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; 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
3ran; the contract check could not run
4ran
2unverified

Licence: 3 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from DTennant/GPC. “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.

DTennant/GPC official repository 11 samples, 9 ran (5 instrument-failed) · 2 unverified
cluster_acc in 33 papers project_utils/cluster_utils.py ran; the contract check could not run (RAISES) MIT (permissive) here; the stored copy is pointer only · 569a0b5d2369b072 · report fixture: signature y_true:ndarray/1/int, y_pred:ndarray/1/int, return_ind:bool/0/bool · returned float64 · level recorded 2026-09-26
conv3x3 in 1,376 papers models/wrn.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 00e569acd6b45ef0 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded, date not recorded
drop_path in 325 papers
census: 27 implementations from 61 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind float, dtype float32
models/vision_transformer.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) here; the stored copy is pointer only · 55120f2026b56aa2 · report fixture: signature x:Tensor/2/float, drop_prob:float/0/float, training:bool/0/bool · returned Tensor · level recorded, date not recorded
evaluate_clustering in 6 papers project_utils/cluster_utils.py ran · our draft was wrong fingerprinted MIT (permissive) · 15d2b95b53f6db9a · report fixture: signature y_true:ndarray/1/int, y_pred:ndarray/1/int · returned tuple · level recorded 2026-09-24
info_nce_logits in 15 papers project_utils/loss_utils.py ran MIT (permissive) · 261eee9d69c08e44 · report fixture: signature features:Tensor/2/float, args:Args/0/?, device:str/0/str · returned tuple · level recorded 2026-09-26
pairwise_NNs_inner project_utils/loss_utils.py ran fingerprinted MIT (permissive) · dbc15099505eb5a0 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-26
pairwise_distance in 55 papers
census: 6 implementations from 7 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
methods/clustering/faster_mix_k_means_pytorch.py ran fingerprinted MIT (permissive) · 9e1769984f0ee4c2 · report fixture: signature data1:Tensor/2/float, data2:Tensor/2/float, batch_size:int/0/int · returned Tensor · level recorded 2026-09-26
proto_for_supcon_logits project_utils/loss_utils.py ran MIT (permissive) · 8fa5d913e26ce4e6 · report fixture: signature q:Tensor/2/float, k:Tensor/2/float, cluster_result:dict/0/?, uq_idxs:Tensor/1/int, all_uq_idxs:Tensor/1/int, sup_con:callable/0/? · returned Tensor · level recorded 2026-09-26
purity_score in 10 papers project_utils/cluster_utils.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · 1645ca2fb55ce1f8 · report fixture: signature y_true:ndarray/1/int, y_pred:ndarray/1/int · returned float64 · level recorded 2026-09-24
vit_small in 33 papers models/vision_transformer.py unverified MIT (permissive) · 995a10f898196998 · report
vit_tiny in 40 papers models/vision_transformer.py unverified MIT (permissive) · 996780ba4be89ba3 · report

Tasks

Contrastive LearningImage ClassificationObject RecognitionRepresentation Learningimage-classification

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Contrastive Learning

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