Session Rating of Perceived Exertion Combined With Training Volume for Estimating Training Responses in Runners
Bibliographic record
Abstract
CONTEXT: Historically, methods of monitoring training loads in runners have used simple and convenient metrics, including the duration or distance run. Changes in these values are assessed on a week-to-week basis to induce training adaptations and manage injury risk. To date, whether different measures of external loads, including biomechanical measures, provide better information regarding week-to-week changes in external loads experienced by a runner is unclear. In addition, the importance of combining internal-load measures, such as session rating of perceived exertion (sRPE), with different external-load measures to monitor week-to-week changes in training load in runners is unknown. OBJECTIVE: To compare week-to-week changes in the training loads of recreational runners using different quantification methods. DESIGN: Case series. SETTING: Community based. PATIENTS OR OTHER PARTICIPANTS: Recreational runners in Vancouver, British Columbia. MAIN OUTCOME MEASURE(S): Week-to-week changes in running time, steps, and cumulative shock, in addition to the product of each of these variables and the corresponding sRPE scores for each run. RESULTS: Sixty-eight participants were included in the final analysis. Differences were present in week-to-week changes for running time compared with timeRPE (d = 0.24), stepsRPE (d = 0.24), and shockRPE (d = 0.31). The differences between week-to-week changes in running time and cumulative shock were also significant at the overall group level (d = 0.10). CONCLUSIONS: We found that the use of an internal training-load measure (sRPE) in combination with external load (training duration) provided a more individualized estimate of week-to-week changes in overall training stress. A better estimation of training stress has significant implications for monitoring training adaptations, resulting performance, and possibly injury risk reduction. We therefore recommend the regular use of sRPE and training duration to monitor training load in runners. The use of cumulative shock as a measure of external load in some runners may also be more valid than duration alone.
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.003 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".