MétaCan
Menu
Back to cohort
Record W4393932787 · doi:10.1515/jqas-2023-0019

Spatial roles in hockey special teams

2024· article· en· W4393932787 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.

Bibliographic record

VenueJournal of Quantitative Analysis in Sports · 2024
Typearticle
Languageen
FieldEconomics, Econometrics and Finance
TopicSports Analytics and Performance
Canadian institutionsMcGill University
Fundersnot available
KeywordsComputer scienceSoftware deploymentFrame (networking)Operations researchArtificial intelligenceMathematics

Abstract

fetched live from OpenAlex

Abstract Special teams (i.e. power play and penalty kill) situations play an outsized role in determining the outcome of ice hockey games. Yet, quantitative methods for characterizing special teams tactics are limited. This work focuses on team structure and player deployment during in-zone special teams possessions. Leveraging player and puck tracking data from the National Hockey League (NHL), a framework is developed for describing player positioning during 5-on-4 power play and 4-on-5 penalty kill possessions. More specifically, player roles are defined directly from the player tracking data using non-negative matrix factorization, and every player is allocated a unique role at every frame of tracking data by solving a linear assignment problem. Team formations naturally arise through the combination of roles occupied in a frame. Roles that vary on a per-frame basis allow for a fine-grained analysis of team structure. This property of the roles-based representation is used to group together similar power play possessions using latent Dirichlet allocation, a topic modelling technique. The concept of assignments, which remain constant over an entire possession, is also introduced. Assignments provide a more stable measure of player positioning, which may be preferable when assessing deployment over longer periods of time.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.071
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0030.002
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.0010.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.279
Teacher spread0.252 · 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