Skip to content

fix: config drift — province_supply=3 on RunPod, should be 1 - #28

Open
pcapriolo wants to merge 1 commit into
mainfrom
fix/config-drift-province-supply
Open

fix: config drift — province_supply=3 on RunPod, should be 1#28
pcapriolo wants to merge 1 commit into
mainfrom
fix/config-drift-province-supply

Conversation

@pcapriolo

Copy link
Copy Markdown
Owner

Summary

  • RunPod has been training at province_supply=3, max_turns=70 since DEVLOG #152 changed the repo config to province_supply=1, max_turns=30. The sync script was never run.
  • Fixed sync script bug: province_supply was listed in RESTART_KEYS but it IS hot-reloadable (trainer.py:218). This false restart warning may have discouraged syncing.
  • Added startup log reminding to sync config after repo changes.
  • Updated training plan to reflect the actual RunPod state.
  • DEVLOG #154 documents the drift with evidence.

Action Required

After merge, run sync_config_to_runpod.sh to push the config. province_supply and max_turns will take effect via hot-reload at the next iteration — no training restart needed.

Evidence (from losses.jsonl)

  • avg_turns: 52-57 (impossible if max_turns=30 were active)
  • draw_rate: 0.68-0.77 (impossible with supply=1)
  • avg_provinces: 0.34-0.48/player (impossible with supply=1)

Test plan

  • Verify sync_config_to_runpod.sh runs cleanly after merge
  • Confirm province_supply=1 and max_turns=30 appear in RunPod trainer startup log
  • Monitor next 5 iterations: avg_turns should drop to ~15-20, draw_rate to ~5%

🤖 Generated with Claude Code

DEVLOG #152 changed province_supply from 3→1 and max_turns from 70→30
in the repo config, but sync_config_to_runpod.sh was never run. RunPod
has been training with the old values for all iterations since.

Also fixes sync script incorrectly listing province_supply as requiring
a restart — it IS hot-reloadable (trainer.py:218).

DEVLOG #154. Action: run sync_config_to_runpod.sh to push correct config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant