MétaCan
Menu
Back to cohort
Record W2931443126 · doi:10.1080/10447318.2019.1597575

Runners’ Perspectives on ‘Smart’ Wearable Technology and Its Use for Preventing Injury

2019· article· en· W2931443126 on OpenAlex

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueInternational Journal of Human-Computer Interaction · 2019
Typearticle
Languageen
FieldMedicine
TopicPhysical Activity and Health
Canadian institutionsRunning Injury ClinicUniversity of Calgary
FundersNatural Sciences and Engineering Research Council of CanadaAlberta Innovates - Technology Futures
KeywordsWearable computerRecreationActivity trackerWearable technologyHuman–computer interactionComputer scienceBitTorrent trackerEmbedded systemArtificial intelligenceEye tracking

Abstract

fetched live from OpenAlex

Understanding the user experience between runners and wearable technology is crucial for designing personalized and effective wearable technology features for injury prevention. Therefore, the overall objective of this study was to understand the attitudes and beliefs for competitive and recreational runners towards wearable technology as well as its potential use for preventing injury. Survey data were drawn from 663 respondents. Competitive runners preferred GPS running watches and were interested in tracking personalized data to optimize running efficiency, whereas recreational runners used mobile phones/apps and wristband activity trackers to increase motivation. All runners believed that basic metrics found in wearable technology were most important for injury prevention; however, more advanced metrics had little importance. This paper illustrates the importance of understanding different user experiences for recreational and competitive runners in relation to wearable technology, and encourages the human-computer interaction research community to identify methods in personalizing complex running-related wearable technology data.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.320
Threshold uncertainty score0.338

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.041
GPT teacher head0.376
Teacher spread0.336 · 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