Home › Code › get_lr_schedule

get_lr_schedule

Syntologyentry name in harvested 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.

get_lr_schedule appears in the code Syntology harvested for 8 papers, as 9 distinct code bodies found in 9 places (a place is one code body under one paper). Of the 8 papers, 6 with a sample that ran: 4 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument. 1 of the code bodies carries a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named get_lr_schedule do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 9 distinct code bodies named get_lr_schedule: 7 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

1ran · honoured contract
0ran · violated contract
2ran · our draft was wrong
1ran; the contract check could not run
3ran
2unverified
1fingerprinted

Licence is a property of each copy, so it is counted per place: 6 of the 9 places are pointer only (Syntology does not serve that copy's text). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

8 papers shown of 8, newest first; 9 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive. Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's 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.

PaperDateFileStatus SyntologyLicence
Sparse Autoencoders Learn Monosemantic Features in Vision-Language Models 3 Apr 2025 explainableml/sae-for-vlm/dictionary_learning/trainers/trainer.py 5207afb32bd9e1ae ran; the contract check could not run (RAISES) no licence file found · pointer only
Sparse Autoencoders Learn Monosemantic Features in Vision-Language Models 3 Apr 2025 explainableml/sae-for-vlm/dictionary_learning/trainers/standard.py 23d3c9ea7f5c1860 ran · our draft was wrong no licence file found · pointer only
Exposing flaws of generative model evaluation metrics and their unfair treatment of diffusion models 7 Jun 2023 Rayhane-mamah/Efficient-VDVAE/efficient_vdvae_jax/model/schedules.py 8c4274c2f8994da8 ran MIT (permissive)
A Neural PDE Solver with Temporal Stencil Modeling 16 Feb 2023 edward-sun/tsm-pde/tsm/utils.py 550992ca2d10fe7e ran · honoured contract fingerprinted no licence file found · pointer only
Energy-Based Contrastive Learning of Visual Representations 10 Feb 2022 1202kbs/ebclr/libs/ebclr.py 9917282e521dbb6b ran · our draft was wrong no licence file found · pointer only
Normalizing flows for atomic solids 16 Nov 2021 deepmind/flows_for_atomic_solids/experiments/utils.py cc8fc123f8db0baa ran Apache-2.0 (permissive)
Logit Pairing Methods Can Fool Gradient-Based Attacks 29 Oct 2018 uds-lsv/evaluating-logit-pairing-methods/tiny_imagenet/model_lib.py b1dbba539c2d86e5 unverified Apache-2.0 (permissive)
Exascale Deep Learning for Climate Analytics 2018-10 (from id) azrael417/mlperf-deepcam/src/deepCam/utils/parsing_helpers.py 7e06dc810e71b002 ran MIT recorded; this copy not marked cleared · pointer only
Evaluating and Understanding the Robustness of Adversarial Logit Pairing 26 Jul 2018 labsix/adversarial-logit-pairing-analysis/model_lib.py bafd53d08c42386a unverified Apache-2.0 recorded; this copy not marked cleared · pointer only

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the 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 under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. 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 cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

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