MétaCan
Menu
Back to cohort
Record W4407902158 · doi:10.1080/19236026.2024.2442905

Testing the application of reliability-based design acceptance criteria (RBDAC) for open pit slopes

2025· article· en· W4407902158 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueCIM Journal · 2025
Typearticle
Languageen
FieldEngineering
TopicGeotechnical Engineering and Analysis
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsReliability engineeringReliability (semiconductor)Acceptance testingComputer scienceEngineeringSoftware engineering

Abstract

fetched live from OpenAlex

Open-pit slope design is increasingly adopting probabilistic approaches. Designs are assessed against design acceptance criteria considering the potential consequences of failure. Mature operations have recognized the importance of optimizing slope configurations by considering design reliability and the potential consequences of slope failure. This parametric study applied quantitative reliability-based design acceptance criteria (RBDAC) to evaluate the factor of safety and probability of failure from probabilistic slope stability analysis for an open-pit slope modified from an actual pit slope in British Columbia, Canada. A matrix of acceptability criteria was used, based on the design reliability and potential economic consequences of failure. The three design reliability levels considered were derived from parameter and geometrical uncertainties by incorporating diverse scenarios, thus reflecting the geotechnical, geological, and hydrogeological characteristics of the implemented pit slope. Other uncertainties include computational simplifications and spatial variability. Results highlight the significant role uncertainty plays in the design process. Using the RBDAC matrix facilitates transparent evaluation of uncertainty, allowing determination and communication of the level of reliability in the design.

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.001
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.887
Threshold uncertainty score0.246

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.029
GPT teacher head0.288
Teacher spread0.259 · 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