MétaCan
Menu
Back to cohort
Record W2287288541

Outbreak: Lessons Learned from Developing a “History Game”

2009· article· en· W2287288541 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueLoading... · 2009
Typearticle
Languageen
FieldArts and Humanities
TopicComics and Graphic Narratives
Canadian institutionsnot available
Fundersnot available
KeywordsContext (archaeology)Tragedy (event)Game DeveloperVideo game designPublic relationsMedia studiesGame designAdvertisingComputer scienceMultimediaSociologyHistoryPolitical scienceBusinessSocial science
DOInot available

Abstract

fetched live from OpenAlex

This paper describes the production of Outbreak, a game focused on the 1885 smallpox epidemic in Montreal. It is a preliminary report on the manner in which, by both theorizing about and building a game, we are responding to some of the questions that have animated the literature on computer games for history. The article begins with a survey of publications by researchers who have studied the capacity of games to support learning, and outlined how these can be used in concert with books and other media. We next provide the context to our project, which was conceived to market a film to be broadcast on television, and support a book on which the film was based – a bestselling history of a preventable tragedy that resulted in the deaths of over 3,000 Montrealers. We outline how we built from the book, creating a game that asked the player to save as many as possible from death, using tools that mimicked that which was available in the late nineteenth century. We conclude by reflecting on the lessons that we learned, and how we will apply these to our present and future projects.

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.000
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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.883
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
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.0020.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.121
GPT teacher head0.276
Teacher spread0.155 · 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