Applying Consequence-Driven Scenario Selection to Lifelines
Bibliographic record
Abstract
We present a new consequence-driven framework for earthquake scenario selection. For emergency managers, utility operators, policy makers, and other stakeholders, a scenario-based seismic risk assessment is often necessary for the purpose of emergency management and planning. In developing a scientifically defensible scenario, stakeholders can simulate a realistic event in order to pre-identify vulnerabilities in the system and support action to address these vulnerabilities. Selecting scenarios is particularly challenging for important population centers and critical infrastructure in stable tectonic environments, such as in the central and eastern United States, where uncertain long-term seismicity and unknown faults offer inadequate constraints. Notably, significant events in these so-called stable regions do occur (e.g., Nahanni, Canada, 1985, M6.9; Tennant Creek, Australia, 1998, M6.7). In regions of low seismicity, even moderate events can be consequential due to the higher vulnerability of buildings typical of such regions when compared to regions of higher seismicity. Furthermore, communicating seismic risk to stakeholders and the general public in these regions can be especially challenging due to the complexities of characterizing the hazard level. This framework has been developed to address these challenges for scenario selection in low seismic hazard regions. In this new approach, the analysis begins instead with the explicit definition of a consequence of concern to the specific stakeholder. This can range from a definition of loss (in lives, dollars, or another metric of interest), or a performance metric for critical infrastructure. The framework leverages United States Geological Survey software to run the hazard and consequence analysis. Driven by this stakeholder-defined consequence, an inversion analysis generates a complete event set of candidate scenarios that could breach this consequence. The final selection of a scenario, or family of scenarios, is then scientifically informed, but not limited by our lack of constraints in characterizing the hazard.
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.008 | 0.027 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.003 |
| Scholarly communication | 0.004 | 0.005 |
| Open science | 0.003 | 0.005 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.009 | 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".