Stall detection: hardcoded heuristics vs LLM judgment #33
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
How should "training is stuck" be detected?Resolved by scope clarification: the training runner does not detect stalls. It outputs structured per-round stats; an external observer (human or LLM) reads them and judges. No heuristics baked in.
The real question becomes: what derived/aggregate stats should the runner include in its output to make stall detection easy for an external reader? Rolling averages? Trend indicators? Or just raw per-round data and let the reader compute?
This merges into #32 (structured output format).
Merged into #32 — stall detection is an external concern; the runner just needs rich enough output.