Define the tunable parameter set #31
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent: #29
Question
Which hyperparameters from PPO_Bot's full inventory should be exposed for LLM-driven tuning?
Candidates (easy to expose, no structural impact):
lr(learning rate) — 3e-4clipEpsilon(PPO clip ratio) — 0.2entropyCoeff(exploration bonus) — 0.01valueLossCoeff— 0.5epochs(PPO updates per batch) — 4miniBatchSize— 64gamma(discount factor) — 0.99lam(GAE lambda) — 0.95maxGradNorm(gradient clipping) — 0.5Candidates (medium risk):
logStdfloor clamp (-3.0) — affects minimum exploration; duplicated in 4 places, needs consolidation firstinitialLogStd(0.0) — only matters at fresh init, not resumeExclude (structural/dangerous):
The LLM needs a bounded, safe set it can experiment with without breaking training.
Resolution
Decision: expose all non-structural hyperparameters.
Full tunable set (11 params, all via
PPOB_*env vars with sensible defaults):Easy (already wired):
PPOB_LR(3e-4)PPOB_CLIP_EPSILON(0.2)PPOB_ENTROPY_COEFF(0.01)PPOB_VALUE_LOSS_COEFF(0.5)PPOB_EPOCHS(4)PPOB_MINI_BATCH_SIZE(64)PPOB_GAMMA(0.99)PPOB_LAM(0.95)PPOB_MAX_GRAD_NORM(0.5)Added in this ticket (with logStd floor consolidation from 4 sites → 1):
PPOB_LOG_STD_FLOOR(-3.0) — minimum exploration clampPPOB_INITIAL_LOG_STD(0.0) — initial logStd on fresh startExcluded (structural/dangerous — would break saved weights or architecture):