MétaCan
Menu
Back to cohort
Record W2366175431

The constructing principle of event tree method and its application in risk analysis for dykes and dams

2006· article· en· W2366175431 on OpenAlex
Dongya Sun

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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of China Institute of Water Resources and Hydropower Research · 2006
Typearticle
Languageen
FieldEngineering
TopicGeoscience and Mining Technology
Canadian institutionsnot available
Fundersnot available
KeywordsEvent tree analysisEvent treeEvent (particle physics)Fault tree analysisReliability (semiconductor)Tree (set theory)Risk analysis (engineering)Flexibility (engineering)Stability (learning theory)Computer scienceField (mathematics)MathematicsEngineeringStatisticsReliability engineeringBusinessMachine learning
DOInot available

Abstract

fetched live from OpenAlex

The constructing principle and method of the event tree is put forward and the probability calculation of branch events is introduced.The event tree method can easily take various kinds of random factors into consideration in reliability analysis of systematic structures.Due to its flexibility in dealing with natural variability and uncertain knowledge,the event tree method is widely used in the field of risk analysis for dykes and dams in countries such as Canada and Australia.A case study on a dyke risk analysis is given in this paper.Three failure modes are supposed,i.e.overtopping,structural stability failure and erosion of foundation.The uncertain factors influencing the given three failure modes and their quantification are interpreted in detail.The result of the analysis reveals the advantages of the event tree method in risk analysis for dykes and dams.

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.306
Threshold uncertainty score0.154

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.000
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.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.017
GPT teacher head0.328
Teacher spread0.311 · 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