Methods › General › Self-Supervised Learning › SimCLR

SimCLR

240 papers tagged archive 2025-07-28

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

SimCLR is a framework for contrastive learning of visual representations. It learns representations by maximizing agreement between differently augmented views of the same data example via a contrastive loss in the latent space. It consists of:

A minibatch of N examples is randomly sampled and the contrastive prediction task is defined on pairs of augmented examples derived from the minibatch, resulting in 2N data points. Negative examples are not sampled explicitly. Instead, given a positive pair, the other 2(N − 1) augmented examples within a minibatch are treated as negative examples. A NT-Xent (the normalized temperature-scaled cross entropy loss) loss function is used (see components).

Source: A Simple Framework for Contrastive Learning of Visual...See Code · google-research/simclr

In Syntology verified reference implementation at level V3; retrieve with get_reference_implementation(name='SimCLR'). The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:2002.05709) is about this method is not checked.

Origin paper of this answer, arXiv:2002.05709 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 115 ran (of which 33 constructed an object rather than computing a result; 89 with no instrument failure: 1 honoured, 1 violated, 87 with no contract checked; 26 where Syntology's instrument failed) · 22 unverified (of 137 harvested samples) · 52 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.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 240 · with a code link: 127 · where Syntology ran a sample: 38 (33 with a run with no instrument failure, 5 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (38 of 240 tagged: 33 with a run with no instrument failure, 5 where every run was a failure of Syntology's instrument)

Page 1 of 3: papers 1 to 100 of 240, 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

20 shown of 202 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
Self-Supervised Learning120
Contrastive Learning116
Representation Learning79
Data Augmentation29
Image Classification22
image-classification16
Transfer Learning15
Linear evaluation11
Object Detection10
Semantic Segmentation10
object-detection10
Classification8
Retrieval8
Activity Recognition7
Clustering7
General Classification7
Human Activity Recognition7
Segmentation7
Benchmarking5
Image Retrieval5

Usage over time archive 2025-07-28

Papers per year tagged with SimCLR: 2020 to 2025, peak 54 54 0 2020: 25 papers 2020 2021: 51 papers 2021 2022: 54 papers 2022 2023: 53 papers 2023 2024: 46 papers 2024 2025: 11 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (240 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

Self-Supervised 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