Retrospective Analysis of Training and Its Response in Marathon Finishers Based on Fitness App Data
Bibliographic record
Abstract
Objective: Finishing a marathon requires to prepare for a 42.2 km run. Current literature describes which training characteristics are related to marathon performance. However, which training is most effective in terms of a performance improvement remains unclear. Methods: We conducted a retrospective analysis of training responses during a 16 weeks training period prior to an absolved marathon. The analysis was performed on unsupervised fitness app data (Runtastic) from 6,771 marathon finishers. Differences in training volume and intensity between three response and three marathon performance groups were analyzed. Training response was quantified by the improvement of the velocity of 10 km runs Δv10 between the first and last 4 weeks of the training period. Response and marathon performance groups were classified by the 33.3rd and 66.6th percentile of Δv10 and the marathon performance time, respectively. Results: Subjects allocated in the faster marathon performance group showed systematically higher training volume and higher shares of training at low intensities. Only subjects in the moderate and high response group increased their training velocity continuously along the 16 weeks of training. Conclusion: We demonstrate that a combination of maximized training volumes at low intensities, a continuous increase in average running speed up to the aimed marathon velocity and high intensity runs ≤ 5 % of the overall training volume was accompanied by an improved 10 km performance which likely benefited the marathon performance as well. The study at hand proves that unsupervised workouts recorded with fitness apps can be a valuable data source for future studies in sport science.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".