MétaCan
Menu
Back to cohort
Record W2594857272 · doi:10.1115/1.4036155

Rare Event Analysis Considering Data and Model Uncertainty

2017· article· en· W2594857272 on OpenAlex
Malak El-Gheriani, Faisal Khan, Ming J. Zuo

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

VenueASCE-ASME Journal of Risk and Uncertainty in Engineering Systems Part B Mechanical Engineering · 2017
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsUniversity of AlbertaMemorial University of Newfoundland
Fundersnot available
KeywordsCategorical variableComputer scienceRare eventsEvent (particle physics)Data miningUncertainty analysisUncertainty quantificationBayesian probabilitySensitivity analysisBayesian networkMachine learningEconometricsArtificial intelligenceStatisticsMathematics

Abstract

fetched live from OpenAlex

Abstract In risk analysis of rare events, there is a need to adopt data from different sources with varying levels of detail (e.g., local, regional, categorical data). Therefore, it is very important to identify, understand, and incorporate the uncertainty that accompanies the data. Hierarchical Bayesian analysis (HBA) addresses uncertainty among the aggregated data for each event through generating an informative prior distribution for the event's parameter of interest. The Bayesian network (BN) approach is used to model accident causation. BN enables both inductive and abductive reasoning, which helps to better understand and minimize model uncertainty. In this work, the methodology is proposed to integrate BN with HBA to model rare events, considering both data and model uncertainty. HBA considers data uncertainty, while BN uses an adaptive model to better represent and manage model uncertainty. Application of the proposed methodology is demonstrated using three types of offshore accidents. The proposed methodology provides a way to develop a dynamic risk analysis approach to rare events.

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.009
metaresearch head score (Gemma)0.009
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.432
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0090.009
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0020.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.056
GPT teacher head0.325
Teacher spread0.270 · 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