Why Don’t Most Runners Get Knee Osteoarthritis? A Case for Per-Unit-Distance Loads
Bibliographic record
Abstract
UNLABELLED: Peak knee joint contact forces ("loads") in running are much higher than they are in walking, where the peak load has been associated with the initiation and progression of knee osteoarthritis. However, runners do not have an especially high risk of osteoarthritis compared with nonrunners. This paradox suggests that running somehow blunts the effect of very high peak joint contact forces, perhaps to provide a load per unit distance (PUD) traveled that is relatively low. PURPOSE: This study aimed to compare peak and PUD knee joint loads between human walking and running. METHODS: Fourteen healthy adults walked and ran at self-selected speeds. Ground reaction force and motion capture data were measured and combined with inverse dynamics and musculoskeletal modeling to estimate the peak knee joint loads, PUD knee joint loads, and the impulse of the knee joint contact force for each gait with a matched-pair (within-subject) design. RESULTS: The peak load was three times higher in running (8.02 vs 2.72 body weight, P < 0.001), but the PUD load did not differ between running and walking (0.80 vs 0.75 body weight per meter, P = 0.098). The impulse of the joint contact force was greater for running than for walking (1.30 vs 1.04 body weight per second, P < 0.001). The peak load increased with increasing running speed, whereas the PUD load decreased with increasing speed. CONCLUSIONS: Compared with walking, the relatively short duration of ground contact and relatively long length of strides in running seem to blunt the effect of high peak joint loads, such that the PUD loads are no higher than that in walking. Waveform features other than or in addition to the peak value should be considered when studying joint loading and injuries.
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.005 | 0.019 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.003 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".