MétaCan
Menu
Back to cohort
Record W3094744489 · doi:10.1115/pvp2020-21054

Pipeline Crack Half-Life Versus 1.10 Safety Factor at Next Inspection

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

VenueVolume 1: Codes and Standards · 2020
Typearticle
Languageen
FieldEngineering
TopicFatigue and fracture mechanics
Canadian institutionsStantec (Canada)
Fundersnot available
KeywordsPipeline (software)Interval (graph theory)Integrity managementPipeline transportComputer scienceReliability engineeringOperator (biology)Asset (computer security)Feature (linguistics)EngineeringComputer securityMathematicsMechanical engineering

Abstract

fetched live from OpenAlex

Abstract Periodic inspection is a proven approach to structural integrity management of transportation systems. This is as true for pipelines as it is for aircraft and railways. Setting the re-inspection interval to ensure imperfections cannot grow to critical dimensions prior to the next inspection is a foundational requirement of this maintenance methodology. API 1176 delineates two methods for re-inspection interval criteria for pipeline crack threat management: (1) maintaining a safety factor of 1.10 and at least a 30% of wall thickness remaining ligament depth until the next inspection, or (2) inspect at the half-life of the feature with the lowest remaining life taking the end of life being a 1.00 safety factor. Recent proposed regulatory documents and draft rules have down-selected to Method (1), or at least demonstrating compliance to Method (1), which will require some operators who have only been using Method (2) to safely manage this change. The two methods are compared for every asset of a large North American operator under current actual operating conditions. The relative conservatism of the two methods is directly compared. Sensitivity to a minimum remaining ligament requirement less than the recommended 30% of wall thickness is explored, and leak/rupture threat differentiation is considered. Implications of the change for a liquids pipeline operator in North America are described.

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 categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.533
Threshold uncertainty score1.000

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.027
GPT teacher head0.238
Teacher spread0.211 · 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