MétaCan
Menu
Back to cohort
Record W1987142500 · doi:10.1080/00140139.2012.752528

Low back loads while walking and carrying: comparing the load carried in one hand or in both hands

2013· article· en· W1987142500 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

VenueErgonomics · 2013
Typearticle
Languageen
FieldMedicine
TopicMusculoskeletal pain and rehabilitation
Canadian institutionsUniversity of Waterloo
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsKinematicsWork (physics)Compression (physics)Load cellHeavy loadStructural engineeringEngineeringMaterials scienceMechanical engineeringPhysicsComposite material

Abstract

fetched live from OpenAlex

This study investigates the consequences of carrying load in one hand versus both hands. Six participants walked carrying buckets containing various weights. The weight was either carried in one hand or distributed evenly between both hands. Electromyography, force plate and body kinematic data were input to a three-dimensional anatomically detailed model of the spine to calculate spine loading. Carrying loads in one hand resulted in more load on the low back than when the load was split between both hands. When carrying 30 kg in one hand, the low back compression exceeded 2800 N; however, splitting the load between hands reduced low back compression to 1570 N (reduction of 44%). Doubling the total load by carrying 30 kg in each hand actually produced lower spine compression than when carrying 30 kg in one hand. Balancing the load between both hands when carrying material has merit and should be considered when designing work. PRACTITIONER SUMMARY: Carrying a load in one hand (30 kg) resulted in more spine load than splitting the same load between both hands (15 kg). When carrying double the load in both hands (30 kg in each hand vs. 30 kg in one hand), spine load decreased, suggesting merit in balancing load when designing work.

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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.098
Threshold uncertainty score0.331

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.027
GPT teacher head0.253
Teacher spread0.226 · 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