MétaCan
Menu
Back to cohort
Record W3043233600 · doi:10.1371/journal.pone.0236047

Shoe feature recommendations for different running levels: A Delphi study

2020· article· en· W3043233600 on OpenAlex
Eric C. Honert, M. Mohr, Wing‐Kai Lam, Sandro Nigg

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenuePLoS ONE · 2020
Typearticle
Languageen
FieldEngineering
TopicLower Extremity Biomechanics and Pathologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsDelphi methodForefootDelphiComputer scienceHeelFeature (linguistics)CrashPhysical medicine and rehabilitationMedicinePhysical therapyArtificial intelligenceSurgery

Abstract

fetched live from OpenAlex

Providing runners with footwear that match their functional needs has the potential to improve footwear comfort, enhance running performance and reduce the risk of overuse injuries. It is currently not known how footwear experts make decisions about different shoe features and their properties for runners of different levels. We performed a Delphi study in order to understand: 1) definitions of different runner levels, 2) which footwear features are considered important and 3) how these features should be prescribed for runners of different levels. Experienced academics, journalists, coaches, bloggers and physicians that examine the effects of footwear on running were recruited to participate in three rounds of a Delphi study. Three runner level definitions were refined throughout this study based on expert feedback. Experts were also provided a list of 20 different footwear features. They were asked which features were important and what the properties of those features should be. Twenty-four experts, most with 10+ years of experience, completed all three rounds of this study. These experts came to a consensus for the characteristics of three different running levels. They indicated that 12 of the 20 footwear features initially proposed were important for footwear design. Of these 12 features, experts came to a consensus on how to apply five footwear feature properties for all three different running levels. These features were: upper breathability, forefoot bending stiffness, heel-to-toe drop, torsional bending stiffness and crash pad. Interestingly, the experts were not able to come to a consensus on one of the most researched footwear features, rearfoot midsole hardness. These recommendations can provide a starting point for further biomechanical studies, especially for features that are considered as important, but have not yet been examined experimentally.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.731
Threshold uncertainty score0.432

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.201
GPT teacher head0.266
Teacher spread0.065 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it