run_walk_cycles
Evaluates whether walk breaks benefit running pace by pairing each walk with the next run block's pace and tracking run pace decay across cycles.
Instructions
M3 run/walk cycle economics — does the walk buy anything? (§17.2)
Args:
run: run_id, activity_id or Garmin file id. Empty means the latest run.
CHOICE, NOT CAPACITY (§6.6). This is how the athlete elected to structure
the run; it says nothing about what they could have done.
`purchase` pairs each walk with the NEXT run block's pace; `decay` is run
pace by cycle index. Both are PAIRED SERIES, never a fitted slope — time
into the run confounds both, and a coefficient over four points is wider
than itself. Read `elapsed_at_*` before concluding the walk caused anything.
Run blocks under the 120 s pace gate report duration but no pace.
WHAT GOVERNED THE WALKS DECIDES WHAT THIS MEASURES, and this build does
not know. If a rule (an HR cap, a clock) decided them, purchase and decay
measure what the STRUCTURE delivered; if the athlete walked when they felt
like it, identical arithmetic measures WILLINGNESS. `walk_protocol` is
"not collected" here, so `poolable_with_other_runs` is false on every run:
structure that has not been established cannot be assumed. Read each run
on its own.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run | No | ||
| last_n | No | ||
| cluster | No | ||
| end_date | No | ||
| run_type | No | ||
| direction | No | ||
| segment_id | No | ||
| start_date | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |