MétaCan
Menu
Back to cohort
Record W184621335 · doi:10.5006/c2007-07686

Assessing Pipeline Vulnerability to Telluric Currents

2007· article· en· W184621335 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 institutionsGeological Survey of Canada
Fundersnot available
KeywordsPipeline (software)Vulnerability (computing)Petroleum engineeringGeologyVulnerability assessmentComputer scienceEnvironmental scienceForensic engineeringMarine engineeringEngineeringMechanical engineeringComputer security

Abstract

fetched live from OpenAlex

Abstract Telluric currents produce variations in pipe-to-soil potential (PSP) that take the pipeline outside the voltage range for cathodic protection and interfere with potential surveys. The size of the PSP variation depends on a variety of factors related both to the natural environment and the characteristics of the pipeline itself. This paper presents a methodology for assessing how different pipeline features influence the vulnerability of the pipeline to telluric effects. Derivation of the distributed-source transmission line (DSTL) equations for induction in a pipeline show that the critical parameters are the series impedance of the pipeline steel and the parallel conductance to ground through the pipeline coating. Large PSP variations occur where there is a disruption in the flow of telluric currents along the pipeline, such as happens at the end of the pipeline, at flanges, at bends, and changes in pipeline characteristics. A series of plots are presented showing the dependence of PSP variations on coating conductance, changes in series impedance and bends in the pipeline. Also examined are how the PSP variations are modified when overlapping effects occur. Finally, the paper considers the effect of various mitigation strategies and presents model results of the reduction in PSP variations that can be achieved.

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.001
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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.849
Threshold uncertainty score0.734

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.001
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.026
GPT teacher head0.315
Teacher spread0.289 · 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