Methods › Reinforcement Learning › Policy Gradient Methods › REINFORCE

REINFORCE

introduced 1999 185 papers tagged archive 2025-07-28

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

REINFORCE is a Monte Carlo variant of a policy gradient algorithm in reinforcement learning. The agent collects samples of an episode using its current policy, and uses it to update the policy parameter θ. Since one full trajectory must be completed to construct a sample space, it is updated as an off-policy algorithm.

∇_θJ(θ) = 𝔼_π[Gₜ∇_θlnπ_θ(Aₜ|Sₜ)]

Image Credit: Tingwu Wang

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: L-REINFORCE; MF-REINFORCE; Buffer-and-Reinforce; Ground-Compose-Reinforce; Reinforce Adjoint Matching (RAM).

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: 185 · with a code link: 80 · where Syntology ran a sample: 24 (20 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (24 of 185 tagged: 20 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument)

Page 1 of 2: papers 1 to 100 of 185, 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 167 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
Reinforcement Learning (RL)59
Reinforcement Learning43
reinforcement-learning42
Neural Architecture Search19
Policy Gradient Methods16
Deep Reinforcement Learning12
Text Generation9
Diversity8
Sentence8
Image Classification7
Q-Learning7
Question Answering7
Decision Making6
GPU6
Image Captioning5
Machine Translation5
Recommendation Systems5
Translation5
image-classification5
Bayesian Optimization4

Usage over time archive 2025-07-28

Papers per year tagged with REINFORCE: 2011 to 2025, peak 31 31 0 2011: 1 paper 2011 2012: 0 papers 2013: 1 paper 2013 2014: 0 papers 2015: 1 paper 2015 2016: 6 papers 2017: 9 papers 2017 2018: 18 papers 2019: 18 papers 2019 2020: 31 papers 2021: 30 papers 2021 2022: 20 papers 2023: 20 papers 2023 2024: 16 papers 2025: 14 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (185 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

Policy Gradient Methods

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