MétaCan
Menu
Back to cohort
Record W4405360834 · doi:10.1115/ipc2024-134129

An Operator’s Experience of Managing the Hard Spot Threat

2024· article· en· W4405360834 on OpenAlexaboutno aff
Gary Vervake, Debartha Bag, Sam Kindel, Oleg Shabarchin, Brady Bolf

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsSweet spotComputer scienceOperator (biology)Hot spot (computer programming)SimulationOperating system

Abstract

fetched live from OpenAlex

Abstract Hard Spots are a recognized pipe manufacturing threat classified under ASME B31.8S for managing system integrity of Natural Gas (NG) transmission pipelines. Hard spots with sufficiently high hardness properties may be susceptible to hydrogen embrittlement and hydrogen stress cracking (HSC). Enbridge experience of managing Hard Spot threat through a Hard Spot ILI program is discussed in this paper. Enbridge has run roughly 2500 miles of Hard Spot tool in its US and Canadian transmission pipelines. Overall tool performance is discussed for both baseline from the perspective of initial Hard Spot callouts and subsequent in-the ditch validation of Hard Spot features. ILI reported Hard Spot features, feature confirmation in the ditch, and subsequent metallurgical laboratory assessment, has been discussed for Enbridge’s gas transmission system. Tool performance has been discussed leveraging Enbridge’s vast mileage of Hard Spot data using API 1163 unity plot methodology comparing tool called features and in-the-ditch and laboratory validation data. Finally, Enbridge’s Bellhole inspection and repair protocol has been discussed specific to related digs for managing the Hard Spot threat.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.009
metaresearch head score (Gemma)0.011
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Case report · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.014
Threshold uncertainty score0.047

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0090.011
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0030.002
Scholarly communication0.0030.003
Open science0.0020.003
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0140.003

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.097
GPT teacher head0.413
Teacher spread0.316 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designCase report
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicRisk and Safety AnalysisFrench-language works237,207