MétaCan
Menu
Back to cohort
Record W2328460904 · doi:10.1115/ipc2010-31269

In-Line Inspection Performance III: Effect of In-Ditch Errors in Determining ILI Performance

2010· article· en· W2328460904 on OpenAlexaff
Rick McNealy, Roger C. McCann, Michael Van Hook, Amanda Stiff, Richard Kania

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicNon-Destructive Testing Techniques
Canadian institutionsTransCanada (Canada)
Fundersnot available
KeywordsReliability engineeringObservational errorReliability (semiconductor)Context (archaeology)Computer sciencePipeline (software)DitchLine (geometry)Field (mathematics)Measurement uncertaintyEngineeringStatisticsPower (physics)Mathematics

Abstract

fetched live from OpenAlex

The performance of in-line inspection tools employed for pipeline integrity assessments has significant impact on the reliability of assessment results and subsequent remediation program. Previous papers by the lead authors established criteria for determining the number of “successful” field validation measurements for establishing whether a tool’s performance should be accepted or rejected and how to assess the tool performance when a claimed performance can be neither rejected nor accepted. This “apparent” validated performance contains both the ILI tool measurement error and the in-ditch measurement error. Determination of the true tool error can have significant impact on the response to ILI feature characterization relating to timing for repairs and justification of re-assessment intervals. Measurement errors, associated with the currently available technologies employed in the field for in-line inspection metal loss validation measurements, are discussed in this paper. The relative effect of variations in validated tool error due to field measurement error on pipeline integrity is discussed within the context of actual in-line assessment case studies.

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.006
metaresearch head score (Gemma)0.028
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.006
Threshold uncertainty score0.030

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.028
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0010.001

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.008
GPT teacher head0.243
Teacher spread0.235 · 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 designObservational
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

Citations8
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicNon-Destructive Testing TechniquesFrench-language works237,207