Comparison of Different Strongman Events: Trunk Muscle Activation and Lumbar Spine Motion, Load, and Stiffness
Bibliographic record
Abstract
Strongman events are attracting more interest as training exercises because of their unique demands. Further, strongman competitors sustain specific injuries, particularly to the back. Muscle electromyographic data from various torso and hip muscles, together with kinematic measures, were input to an anatomically detailed model of the torso to estimate back load, low-back stiffness, and hip torque. Events included the farmer's walk, super yoke, Atlas stone lift, suitcase carry, keg walk, tire flip, and log lift. The results document the unique demands of these whole-body events and, in particular, the demands on the back and torso. For example, the very large moments required at the hip for abduction when performing a yoke walk exceed the strength capability of the hip. Here, muscles such as quadratus lumborum made up for the strength deficit by generating frontal plane torque to support the torso/pelvis. In this way, the stiffened torso acts as a source of strength to allow joints with insufficient strength to be buttressed, resulting in successful performance. Timing of muscle activation patterns in events such as the Atlas stone lift demonstrated the need to integrate the hip extensors before the back extensors. Even so, because of the awkward shape of the stone, the protective neutral spine posture was impossible to achieve, resulting in substantial loading on the back that is placed in a weakened posture. Unexpectedly, the super yoke carry resulted in the highest loads on the spine. This was attributed to the weight of the yoke coupled with the massive torso muscle cocontraction, which produced torso stiffness to ensure spine stability together with buttressing the abduction strength insufficiency of the hips. Strongman events clearly challenge the strength of the body linkage, together with the stabilizing system, in a different way than traditional approaches. The carrying events challenged different abilities than the lifting events, suggesting that loaded carrying would enhance traditional lifting-based strength programs. This analysis also documented the technique components of successful, joint-sparing, strongman event strategies.
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 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.007 | 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".