Increased Vertical Impact Forces and Altered Running Mechanics with Softer Midsole Shoes
Bibliographic record
Abstract
To date it has been thought that shoe midsole hardness does not affect vertical impact peak forces during running. This conclusion is based partially on results from experimental data using homogeneous samples of participants that found no difference in vertical impact peaks when running in shoes with different midsole properties. However, it is currently unknown how apparent joint stiffness is affected by shoe midsole hardness. An increase in apparent joint stiffness could result in a harder landing, which should result in increased vertical impact peaks during running. The purpose of this study was to quantify the effect of shoe midsole hardness on apparent ankle and knee joint stiffness and the associated vertical ground reaction force for age and sex subgroups during heel-toe running. 93 runners (male and female) aged 16-75 years ran at 3.33 ± 0.15 m/s on a 30 m-long runway with soft, medium and hard midsole shoes. The vertical impact peak increased as the shoe midsole hardness decreased (mean(SE); soft: 1.70BW(0.03), medium: 1.64BW(0.03), hard: 1.54BW(0.03)). Similar results were found for the apparent ankle joint stiffness where apparent stiffness increased as the shoe midsole hardness decreased (soft: 2.08BWm/º x 100 (0.05), medium: 1.92 BWm/º x 100 (0.05), hard: 1.85 BWm/º x 100 (0.05)). Apparent knee joint stiffness increased for soft (1.06BWm/º x 100 (0.04)) midsole compared to the medium (0.95BWm/º x 100 (0.04)) and hard (0.96BWm/º x 100 (0.04)) midsoles for female participants. The results from this study confirm that shoe midsole hardness can have an effect on vertical impact force peaks and that this may be connected to the hardness of the landing. The results from this study may provide useful information regarding the development of cushioning guidelines for running shoes.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 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".