MétaCan
Menu
Back to cohort
Record W2083684564 · doi:10.1115/ipc2008-64478

Dealing With Knowledge Uncertainties in Pipeline Reliability Based Design and Assessment

2008· article· en· W2083684564 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsCentre For Cold Ocean Resources EngineeringTransCanada (Canada)
Fundersnot available
KeywordsReliability (semiconductor)RandomnessComputer scienceReliability engineeringUncertainty quantificationRange (aeronautics)Pipeline (software)Confidence intervalRandom variableReliability theoryLimit (mathematics)Probability distributionData miningFailure rateStatisticsEngineeringMathematicsMachine learning

Abstract

fetched live from OpenAlex

Knowledge uncertainties result from limitations of the data and other information required to define parameters that are used in estimating reliability with respect to a given failure threat. The parameters affected typically represent distribution parameters of input random variables used in the calculation; for example, the mean corrosion growth rate for a given pipeline segment. Knowledge uncertainties are distinct from randomness, which is typically manifested in variations in the basic input parameters affecting a given limit state; for example, variations in the excavator force applied to the pipeline in different impact events. Randomness is reflected in the probability distributions used to model the input variables affected and is automatically built into the reliability estimate. However, the reliability estimate is conditional on the values used for parameters affected by knowledge uncertainty. Since these parameters can take a range of values with different probabilities, knowledge uncertainty is best represented as a distribution or confidence interval on the calculated failure probability. Two approaches are proposed to deal with knowledge uncertainties in Reliability Based Design and Assessment (RBDA) applications in which design and operational choices are accepted if they meet a specified reliability target. The first is a formal approach in which reliability targets must be met with a specified level of confidence (e.g. meet the reliability targets with 90% confidence). The second approach is an informal one in which a single conservative value is used for each parameter affected by knowledge uncertainties. Although this approach relies on the judgment of the user, it has the advantage of being simple. In the context of standardizing RBDA, it is recommended that epistemic uncertainty be identified as an important issue that must be considered in demonstrating compliance. It is also recommended that both formal and informal approaches be permitted as viable means of accounting for epistemic uncertainty. The informal approach should be included as a minimum requirement, whereas the formal approach should be presented as an option. This recommended strategy addresses epistemic uncertainty without creating a significant obstacle to the application of RBDA.

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.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: Empirical · Consensus signal: Empirical
Teacher disagreement score0.197
Threshold uncertainty score0.396

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.025
GPT teacher head0.257
Teacher spread0.232 · 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