MétaCan
Menu
Back to cohort
Record W1967948556 · doi:10.1115/ipc2010-31167

Guidance for Selecting SCC Direct Assessment Locations and Estimation of Re-Inspection Intervals

2010· article· en· W1967948556 on OpenAlex
Fraser King, Mark Piazza, Robert Worthingham

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

Venue2010 8th International Pipeline Conference, Volume 1 · 2010
Typearticle
Languageen
FieldEngineering
TopicConcrete Corrosion and Durability
Canadian institutionsTransCanada (Canada)
Fundersnot available
KeywordsStress corrosion crackingComputer sciencePipeline transportField (mathematics)Forensic engineeringData miningEngineeringData scienceCorrosionMechanical engineeringMathematics

Abstract

fetched live from OpenAlex

A significant amount of research and development has been carried out on the mechanism of the stress corrosion cracking of underground pipelines. This paper describes the results of a study, co-funded by PRCI, the US DOT, and pipelines companies, to bring together the results of these various studies in the form of a set of guidelines that will assist companies in identifying the most likely SCC locations on their systems and in predicting how frequently inspection or other mitigation is required. The guidelines have been developed along mechanistic lines, and are divided into four “steps” representing: susceptibility to SCC, crack initiation, early-stage growth and dormancy, and crack growth to failure. For each step, a series of Research Guidelines has been derived from the results of individual research papers or studies. These Research Guidelines may or may not be easily validated against field data. The SCC Guidelines were then developed based on one or more Research Guidelines. Wherever possible, the SCC Guidelines have been validated against field data, but in some cases currently un-testable SCC Guidelines were defined because they offer a potentially unique opportunity to identify where and when SCC might occur.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.936
Threshold uncertainty score0.598

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
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.0000.000
Insufficient payload (model declined to judge)0.0000.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.293
Teacher spread0.274 · 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