MétaCan
Menu
Back to cohort
Record W4409503373 · doi:10.5006/mpwt19-14353

Validating ILI Run with and without Data Loss

2019· article· en· W4409503373 on OpenAlexaboutno aff
Ahmad Al Saif

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldDecision Sciences
TopicSimulation Techniques and Applications
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceData lossOperating system

Abstract

fetched live from OpenAlex

Abstract In-Line Inspection (ILI) technology is considered one of the safest and most efficient and reliable inspection method to inspect hydrocarbon pipelines. The retrieved data are usually validated and verified upon successful completion of the inspection. This paper is intended to introduce a new approach to validate the ILI run based on a statistical analysis comparing the new ILI run with a previous ILI run of the same pipeline by leveraging a root mean square (RMS) model to quantify the similarity between the datasets. API-1163 and Canadian Energy Pipeline Association (CEPA) offer consistent criteria as a validation methodology for a new ILI run. Also, this paper will demonstrate a new scoring criterion for accepting Magnetic Flux Leakage (MFL) runs with partial data loss as number of MFL runs experience unexpected data loss, which might affect the minimum reporting threshold of the tool. The approach will help pipeline operators to identify the criticality of the missed data via a detailed comparison with the previous MFL run for the same pipeline and detailed analysis of the behavior of the tool during the run. The scoring criteria is aligned with the Pipeline Operators Forum (POF) requirements for data loss. Multiple case studies extracted from actual data will be presented throughout the paper.

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 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.001
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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.764
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.0010.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.216
GPT teacher head0.461
Teacher spread0.245 · 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 teacher head, not a consensus.

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

Citations0
Published2019
Admission routes1
Has abstractyes

Explore more

Same topicSimulation Techniques and ApplicationsFrench-language works237,207