MétaCan
Menu
Back to cohort
Record W2036954374 · doi:10.1504/ijcis.2013.058170

Simulation and anticipation of domino effects among critical infrastructures

2013· article· en· W2036954374 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueInternational Journal of Critical Infrastructures · 2013
Typearticle
Languageen
FieldEngineering
TopicInfrastructure Resilience and Vulnerability Analysis
Canadian institutionsPolytechnique Montréal
FundersPolytechnique Montréal
KeywordsDominoDomino effectAnticipation (artificial intelligence)Risk analysis (engineering)Computer scienceInterdependenceComputer securityOrder (exchange)Dialog boxBusiness

Abstract

fetched live from OpenAlex

Interdependencies among critical infrastructures (CIs) are the cause of domino effects that may have serious consequences for society. To limit the consequences of these phenomena, it is important to be able to anticipate any situation that may trigger a domino effect. To do so, it is necessary to have a good understanding of how CIs are interlinked and how they rely on each other to properly operate. Once this achieved, a system must be put in place in order to model the possible propagation of domino effects and to alert the right people at the right time in order for them to take proper action. This paper presents a prototype of an early warning system (EWS) designed to anticipate and model the propagation of failures among CIs. Called DOMINO, this system makes it possible to rapidly visualise, in time and space, the propagation of a domino effect and to promptly identify the critical infrastructures potentially impacted. Along with effective communication systems, such tool can facilitate the exchange of relevant information between infrastructures operators and managers enabling them to put in place mitigation measures and to limit the consequences of domino effects.

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.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.681
Threshold uncertainty score0.740

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.001
Scholarly communication0.0000.001
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.005
GPT teacher head0.294
Teacher spread0.289 · 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