Repository navigation
v0.3.1 — synthetic athletes
The synthetic-athletes release. Eight simulated runners now go through sixteen weeks of the app, day by day against the real tools. Then the release checks whether a coach behaved over the whole course the way a runner would expect. They found two planner bugs, both fixed.
uv tool install git+https://github.com/edxleon/runcoach-ai@v0.3.1
runcoach serveFixed: small weeks
- When a week's budget was too small for the planned days, the planner cut the easy runs and kept both quality sessions at their old size. The result was a three-day week of VO2max, threshold and the long run, or a single VO2max session as the whole week.
- Because the remaining sessions kept their size, such a week could never grow. A runner coming back from a pause stayed at 70 minutes a week for good.
- Now a small budget gets a shorter week, built like any other: one quality session at three days, never only hard sessions, scaled to the budget.
Fixed: the week after the return
- After a full return week (4 × 24 min), the next week came out smaller than it: 72 instead of at least 96 minutes. The median of the weeks since the pause lagged behind the climb.
- In the four weeks after a pause, the week now grows from the last seven days.
Synthetic athletes (evals/sim.py)
- Eight runners:
- one who follows the plan
- one who skips 40 % of the sessions
- three weeks off
- ill for five days
- always runs harder than planned
- VO2max plateau
- no zone detail
- no plan at all
- What they check, over the whole course:
- no hard day when ill or right after a hard run
- the first week back from a pause is easy
- no week far above what was actually run
- no week of mostly hard sessions
- a lighter week at regular intervals
- a plateau gets measured
- after a pause, the weeks climb back to 70 % of before
uv run python evals/sim.py pause_and_returnprints the course week by week.RUNCOACH_SIM_SEEDS=40sweeps 40 more seeds per runner with the events moved around.- 320 courses pass after the fixes.
- Honest limits: the simulated body is a toy, so this shows that the rules behave, not that the training works. It also finds only what its data model knows, so the test on a real account stays.
Evals: 29/29
- Four eval inputs are now a day of a simulated course, pinned byte for byte against what the tools said that day.
- Two new cases:
- the days after a pause stay easy, however good the legs feel;
- a week held on Garmin's load ratio is not raised on request. This is a new rule in
coach.md.
- Both new cases fail without the skill files.
Verified
- 811 Python tests and 66 frontend tests, on Linux, Windows and macOS with Python 3.12 and 3.13, plus the install-as-a-user job.
Not affiliated with Garmin. A training tool, not medical advice.