You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: configs/ablations/ladder/README.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,11 +43,13 @@ Each run config carries a `ladder_rules` block controlling what it takes to clea
43
43
44
44
```yaml
45
45
ladder_rules:
46
-
min_round_win_fraction: 0.5# must win strictly more than this fraction of rounds
47
-
win_last_k: 1# ...and must win the last K rounds (1 == just the final round)
46
+
min_round_wins: 2# must win >= this many of the agent rounds to advance (round 0 excluded)
47
+
win_last_k: 0# ...and must win the last K rounds (1 == just the final round, 0 == disabled)
48
48
```
49
49
50
-
The defaults shown above reproduce the historical behavior (strict majority of rounds **and** win the final round); the block is optional and falls back to these values if omitted. Validation:
50
+
Both keys are **required** — there are no defaults; a config that omits either one errors out. `min_round_wins` is a whole number: the player advances when `player_wins >= min_round_wins`. The baseline round 0 (identical, un-edited codebases) is excluded, so with `tournament.rounds: 5` there are 5 scored agent rounds (rounds 1–5). Validation:
51
51
52
-
- `win_last_k` must be an integer with `1 <= win_last_k <= tournament.rounds`.
53
-
- `min_round_win_fraction` must be a number in `[0, 1)`; `0` drops the majority requirement (e.g. `min_round_win_fraction: 0` + `win_last_k: 1` means "just win the final round").
52
+
- `min_round_wins`must be an integer with `1 <= min_round_wins <= tournament.rounds`.
53
+
- `win_last_k`must be an integer with `0 <= win_last_k <= min_round_wins`. `0` **disables** the trailing-rounds requirement; `1` means "just win the final round".
54
+
55
+
The per-rung outcome (`player_wins`, `won_last_k`, `cleared`) is persisted under `ladder_advancement` in each rung's `metadata.json`. The overall climb result (`rungs_cleared`, `final_opponent`, `cleared_ladder`, …) is written to a ladder-level `metadata.json` in the run's parent dir.
0 commit comments