A goalkeeper’s performance in stopping free kicks reduces when the defensive wall blocks their initial view of the ball
Bibliographic record
Abstract
Free kicks are an important goal scoring opportunity in football. It is an unwritten rule that the goalkeeper places a wall of defending players with the aim of making scoring harder for the attacking team. However, the defensive wall can occlude the movements of the kicker, as well as the initial part of the ball trajectory. Research on one-handed catching suggests that a ball coming into view later will likely delay movement initiation and possibly affect performance. Here, we used virtual reality to investigate the effect of the visual occlusion of the initial ball trajectory by the wall on the performance of naïve participants and skilled goalkeepers. We showed that movements were initiated significantly later when the wall was present, but not by the same amount as the duration of occlusion (~200ms, versus a movement delay of ~70-90ms); movements were thus initiated sooner after the ball came into view, based on less accumulated information. For both naïve participants and skilled goalkeepers this delayed initiation significantly affected performance (i.e., 3.6cm and 1.5cm larger spatial hand error, respectively, not differing significantly between the groups). These performance reductions were significantly larger for shorter flight times, reaching increased spatial errors of 4.5cm and 2.8cm for both groups, respectively. Further analyses showed that the wall-induced performance reduction did not differ significantly between free kicks with and without sideward curve. The wall influenced early movement biases, but only for free kicks with curve in the same direction as the required movement; these biases were away from the final ball position, thus hampering performance. Our results cannot suggest an all-out removal of the wall-this study only considered one potential downside-but should motivate goalkeepers to continuously evaluate whether placing a wall is their best option. This seems most pertinent when facing expert free kick takers for whom the wall does not act as a block (i.e., whose kicks consistently scale the wall).
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.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 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.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.005 | 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".