Effects of an In-season Plyometric Training Program on Repeated Change of Direction and Sprint Performance in the Junior Soccer Player
Bibliographic record
Abstract
Hammami, M, Negra, Y, Aouadi, R, Shephard, RJ, and Chelly, MS. Effects of an in-season plyometric training program on repeated change of direction and sprint performance in the junior soccer player. J Strength Cond Res 30(12): 3312-3320, 2016-We aimed to determine the gains in explosive movements of male junior soccer players induced by incorporating an 8-week plyometric training program (PTP) into a standard soccer conditioning regimen 5 months after the beginning of the competitive season. Our hypothesis was that PTP would enhance explosive movements, and thus sprint running, repeated shuttle sprint ability (RSSA), agility and the ability to make repeated changes of direction (RCOD). A group of junior soccer players were randomly divided into 2 groups: an experimental group (E, n = 15, age 15.7 ± 0.2 years) and a control group (C, n = 13, age 15.8 ± 0.2 years). The participants in E and C performed training exercises and matches together, but for an 8-week period in the latter part of the season, the experimental group replaced a part of the normal regimen (the tactical session) by a biweekly course of PTP (hurdle and drop jumps). Two familiarization sessions were held 2 weeks before definitive testing. The ability of the players was assessed by 3 agility tests (a sprint test with 180° turns, a 9-3-6-3-9 m sprint with backward and forward running, and a four 5-m sprint test with turns); 2 repeated sprint tests (RSSA and RCOD); and running times over 5-, 10-, 20-, 30-, and 40-m distances. Participants in E showed gains relative to C in sprint times (p ≤ 0.05 for 5, 10, and 20 m), and 2 of 3 the RCOD parameters (RCOD best, p ≤ 0.001; RCOD total, p ≤ 0.05). However, with the pattern of plyometric training that we adopted, and perhaps because participants were in good initial physical condition, the agility and RSSA test scores remained unchanged. Nevertheless, we conclude that our PTP can be commended to junior soccer players as a means of improving important components of their physical performance.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".