MétaCan
Menu
Back to cohort
Record W2005707828 · doi:10.1115/ipc2008-64536

Revised Corrosion Management With Reliability Based Excavation Criteria

2008· article· en· W2005707828 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 institutionsTransCanada (Canada)
Fundersnot available
KeywordsIntegrity managementReliability (semiconductor)Reliability engineeringExcavationPipeline transportComputer sciencePipeline (software)Forensic engineeringEngineeringGeotechnical engineering

Abstract

fetched live from OpenAlex

For decades, TransCanada Pipelines has used inline inspection (ILI) to manage the threat of corrosion on gas pipelines. Immediate integrity was addressed using rupture pressure ratio and leak criteria, and future integrity was addressed using a growth assessment. However, a review of excavations based on predictions of defect growth shows that few excavations actually lead to repairs. This study investigated the areas of undue conservatism in both the integrity assessments and the excavation criteria. All aspects of the immediate and future integrity assessment based on ILI were examined. All relevant uncertainties were accounted for in calculating the reliability of the pipeline. A new basis of defining excavation criterion was established based on a reliability assessment and calibration. This criterion was validated against previous ILI based excavations which reveal the features that actually required repair. The criterion was also compared to reliability based criteria recommended in Annex O of the CSA Z662 which gives guidelines for Reliability Based Design and Assessment. This paper addresses the practical limitation of data and presents methods for extracting best information from available data. Case studies that demonstrate the application of the revised assessment method and criterion are also discussed.

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.075
Threshold uncertainty score0.973

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.0010.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.012
GPT teacher head0.217
Teacher spread0.204 · 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