MétaCan
Menu
Back to cohort
Record W2888314871 · doi:10.1515/jhsem-2017-0007

Disaster Risk Analysis Part 1: The Importance of Including Rare Events

2018· article· en· W2888314871 on OpenAlex
David Etkin, Aaida Mamuji, Lee Clarke

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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Homeland Security and Emergency Management · 2018
Typearticle
Languageen
FieldSocial Sciences
TopicDisaster Management and Resilience
Canadian institutionsYork University
Fundersnot available
KeywordsFutures studiesRisk analysis (engineering)Risk managementOperationalizationRare eventsRisk assessmentEstimationEmergency managementBusinessEnvironmental planningActuarial scienceComputer scienceGeographyEngineeringComputer securityEconomicsStatisticsEconomic growthMathematics

Abstract

fetched live from OpenAlex

Abstract Rare events or worst-case scenarios are often excluded from disaster risk analysis. Their inclusion can be very challenging, both from methodological and data availability perspectives. We argue that despite these challenges, not including worst-case scenarios in disaster risk analysis seriously underestimates total risk. It is well known that disaster data sets generally have fat tails. In this paper we analyze data for a number of disaster types in order to empirically examine the relative importance of the few most damaging events. The data show consistent fat-tail trends, which suggests that rare events are important to include in a disaster risk analysis given their percentage contributions to cumulative damage. An example of biased risk estimation is demonstrated by a case study of risk analysis of tanker spills off the western coast of Canada. Incorporating worst-case scenarios into disaster risk analysis both reduces the likelihood of developing fantasy planning documents, and has numerous benefits as evidenced by applications of foresight analysis in the public sector. A separate paper "Disaster Risk Analysis Part 2" explores how disaster risk analyses are operationalized in governmental emergency management organizations, and finds evidence of a systemic underestimation of risk.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.352
Threshold uncertainty score0.754

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.021
GPT teacher head0.308
Teacher spread0.287 · 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