Token Lab検索

← 強化学習ライブラリ
RL / 8 OF 8

Does RL actually improve capability?

Make a falsifiable claim with independent evidence.

Detailed technical articles are available in English and Chinese. This locale shows the English article with localized navigation.

Study guide & lesson outlineLEARNING CONTRACT

Understand → implement → investigate

Goal: explain the mechanism in this lesson, reproduce one example and test a failure case. Reading alone does not mark mastery.

  • Understand: state assumptions, shapes/units and a counterexample.
  • Implement: reproduce a numerical example and inspect boundaries.
  • Investigate: compare one alternative under a matched budget.

Understand the mechanism

Define capability in observable terms: task success on unseen inputs, robustness to perturbations, calibration, cost or constraint satisfaction. Match inference budgets before comparing training recipes. Reward optimization, preference win rate and factual correctness are different endpoints. Include failure slices, uncertainty and a baseline that received a fair tuning budget.

Text / 原始公式
Claim → held-out tasks → matched budgets → uncertainty → failure audit
Report both pass@1 and any best-of-k protocol separately.

Mechanism map & worked derivation

Predeclare comparison → Collect independent runs → Estimate effect and uncertainty → Audit failures and selection
Original schematic; read the steps from top to bottom. SVG ↓
Symbols and assumptions
SymbolMeaning
Scientifically matched pair difference
s_dSample standard deviation of differences
nIndependent pairs, not repeated calls on one item
  1. Use differences [1,2,3]. Their mean is 2 and sample standard deviation is 1. The estimated standard error is 1/√3≈0.577350.
  2. Multiplying by 1.96 gives an illustrative normal half-width 1.131607. With only three pairs and unknown variance, that normal approximation is weak; do not report it as a reliable small-sample interval.
  3. Bootstrapping should resample whole independent units. If several rows belong to one task or user, consider cluster-level resampling rather than pretending rows are independent.
Experiment checkpoint

A small interval can coexist with a biased experiment. Check leakage, selection and tuning budgets separately.

Original exercise & analysis

Write a preregistration for one RL improvement claim: primary metric, minimum useful effect, dataset split, training budget, inference budget, seed count and stopping rule. Prepare a table of alternative explanations and the control that would rule each out.

Passing a reproduction checklist is not reproducing a result. A model can game a verifier or improve average performance while failing an important subgroup.

What evidence would make you reject your improvement claim?

A matched-budget baseline erasing the gain, contamination, wide uncertainty around a negligible effect, or a critical regression can each invalidate the proposed conclusion. Specify these conditions before running the study.

Study evidence & continue

Deep RL that Matters ↗
Build a reproduction protocol →
MATHEMATICAL REVIEW · 2026-10-26

Assumptions, implementation & acceptance

s/√n assumes IID independent experimental units with finite variance. A normal 1.96 interval is approximate and fragile at small n; compare a Student-t interval. Episodes from one training seed are not independent training runs.

Formula conditions, units and worked arithmetic reviewed. The implementation isolates one numerical mechanism; it does not train a policy or control real hardware.

Before running: predict a boundary case

Sample variance is 2.5 and SE is sqrt(0.5); episodes cannot replace independent seeds.

Hint: isolate the assumption

Keep the baseline input fixed, change one parameter or boundary, and compare both the numerical result and the claimed units. A passing example verifies this fixture only.

Minimal executable example

Save the example and linked modules in one folder. Use Node.js 22 or newer, then run node rl-evaluation.mjs. No third-party runtime dependencies.

const solve=()=>{
const differences=[1,2,3,4,5], n=differences.length;
const mean=differences.reduce((a,b)=>a+b)/n;
const variance=differences.reduce((s,x)=>s+(x-mean)**2,0)/(n-1);
return [mean,Math.sqrt(variance/n)];
};
const actual=solve();
const expected=[3,0.7071067811865476];
if(JSON.stringify(actual)===JSON.stringify(expected)){console.log('PASS',actual)}else{
const a=[actual].flat(), b=[expected].flat();
if(a.length!==b.length||a.some((v,i)=>!Number.isFinite(v)||Math.abs(v-b[i])>1e-10))throw Error('Numerical mismatch');
console.log('PASS within 1e-10',actual);
}
Reference output — reveal after predicting
[
  3,
  0.7071067811865476
]

Test and transfer

Sample variance is 2.5 and SE is sqrt(0.5); episodes cannot replace independent seeds.

Record input, code version, expected result and observed result in the notebook below. Then construct a counterexample that violates the assumption above and explain why the original conclusion no longer follows.

Download complete kit (.tar.gz) · Complete reference kit and regression checks

Predict, test and keep evidence

Before revealing an answer, predict one result. After the exercise, record the discrepancy and a transfer test. Saved locally across language editions.

Open notebook / export / clear →

The mathematical review scope is recorded per lesson. It does not establish empirical paper reproduction; report suspected errors in your notes. Review scope