MétaCan
Menu
Back to cohort
Record W3016374459 · doi:10.5006/37692-ch13

Investigation into Possible AC Corrosion from a Cathodic Protection Groundbed

2025· book-chapter· en· W3016374459 on OpenAlex
Wolfgang Fieltsch, Fation Shahinas

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
Typebook-chapter
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsStantec (Canada)
Fundersnot available
KeywordsCathodic protectionCorrosionMaterials scienceMetallurgyGalvanic anodeForensic engineeringEngineeringChemistryElectrochemistryElectrode

Abstract

fetched live from OpenAlex

Abstract This case study involves an investigation into corrosion anomalies on a 4 km long NPS 6 liquid pipeline that interconnects two facilities in an urban setting. An in-line inspection (ILI) in 2017 identified 70 external corrosion anomalies, with two of them exceeding 55% wall loss. An additional five corrosion anomalies had been previously repaired. Recent annual cathodic protection (CP) surveys, and a close-interval potential survey conducted in 2015, all indicate good cathodic protection levels along the line. AC voltages as high as 6 V were measured along the pipeline and were initially thought to be related to a 0.6 km parallel with a high voltage powerline. AC coupons were installed and AC current densities of up to 1400 A/m2 and DC current densities of 2100 A/m2 were recorded in this area, indicating a severe AC corrosion risk. Waveforms indicated that most of the AC voltage was 120 Hz frequency, and that very little of the AC voltage was related to the fundamental 60 Hz powerline frequency. This paper discusses the testing performed to confirm the source of the elevated AC current densities and quantify the associated corrosion risk. The mitigation strategy employed to address this risk is provided.

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 categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Other · Consensus signal: Other
Teacher disagreement score0.511
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.0010.001
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.019
GPT teacher head0.212
Teacher spread0.192 · 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