MétaCan
Menu
Back to cohort
Record W3011125477 · doi:10.1016/j.ress.2020.106934

Dynamic vulnerability assessment of process plants with respect to vapor cloud explosions

2020· article· en· W3011125477 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.

Bibliographic record

VenueReliability Engineering & System Safety · 2020
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsToronto Metropolitan University
FundersChina Scholarship Council
KeywordsOverpressureVulnerability (computing)Identification (biology)Event treeProcess (computing)Event (particle physics)Cloud computingEnvironmental scienceProcess safetyFault tree analysisComputer scienceIgnition systemEvent tree analysisReliability engineeringForensic engineeringRisk analysis (engineering)EngineeringComputer securityChemical plantAerospace engineeringEnvironmental engineering

Abstract

fetched live from OpenAlex

Vapor cloud explosion (VCE) accidents in recent years such as the Buncefield accident in 2005 indicate that VCEs in process plants may lead to unpredicted overpressures, resulting in catastrophic disasters. Although a lot of attempts have been done to assess VCEs in process plants, little attention has been paid to the spatial-temporal evolution of VCEs. This study, therefore, aims to develop a dynamic methodology based on discrete dynamic event tree to assess the likelihood of VCEs and the vulnerability of installations. The developed methodology consists of six steps: (i) identification of hazardous installations and potential loss of containment (LOC), (ii) analysis of vapor cloud dispersion, (iii) identification and characterization of ignition sources, (iv) explosion frequency and delayed time assessment using the dynamic event tree, (v) overpressure calculation by the Multi-Energy method and (vi) damage assessment based on probit models. This methodology considers the time dependencies in vapor cloud dispersion and in the uncertainty of delayed ignitions. Application of the methodology to a case study shows that the methodology can reflect the characteristics of large VCEs and avoid underestimating the consequences. Besides, this study indicates that ignition control may be regarded as a delay measure, effective emergency actions are needed for preventing VCEs.

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.004
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-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.266
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
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.033
GPT teacher head0.334
Teacher spread0.301 · 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