Methods › General › Learning Rate Schedules › Polynomial Rate Decay

Polynomial Rate Decay

10 papers tagged archive 2025-07-28

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

Polynomial Rate Decay is a learning rate schedule where we polynomially decay the learning rate.

In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.

Near matches the lookup lists, each a different name: RATE; RATE; RATE-FT; Decay RNN; committal rate; event rate (ER); Rate Norm Layer; polynomial trees.

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: 9 · where Syntology ran a sample: 6 (5 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (6 of 10 tagged: 5 with a run with no instrument failure, 1 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

20 shown of 24 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
Semantic Segmentation5
Image Segmentation3
Object Detection3
Real-Time Object Detection3
Dichotomous Image Segmentation2
Image Classification2
Object2
Real-Time Semantic Segmentation2
Scene Parsing2
Segmentation2
Thermal Image Segmentation2
2D Semantic Segmentation1
3D Object Detection1
Attribute1
BIG-bench Machine Learning1
Computational Efficiency1
Data Augmentation1
General Classification1
Lesion Segmentation1
Medical Image Analysis1

Usage over time archive 2025-07-28

Papers per year tagged with Polynomial Rate Decay: 2016 to 2022, peak 3 3 0 2016: 3 papers 2016 2017: 1 paper 2017 2018: 2 papers 2018 2019: 2 papers 2019 2020: 1 paper 2020 2021: 0 papers 2021 2022: 1 paper 2022
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

Learning Rate Schedules

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