Approach to Assessment of Corrosion Growth in Pipelines
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.
Bibliographic record
Abstract
Two key components of corrosion growth assessment in pipelines are accurate determination of corrosion growth rate and application of corrosion growth to future integrity of a pipeline. PII has developed a corrosion growth assessment tool, Run Comparison (RunCom) software that allows accurate determination of corrosion growth. RunCom compares the raw signals of the same defect present in two inspection runs to report the real active corrosion defects and their growth with less error. Since variations in corrosion growth along the pipeline can be significant, a single value of average or maximum corrosion growth rate does not represent the corrosion condition of the pipeline and could result in a conservative or non-conservative conclusion for future integrity. PII introduces a Decision Tree Analysis method to categorize the corroded regions along the pipeline and calculate the mean corrosion growth rates in these specific areas. Relationships between corrosion growth rate and defect geometry are also identified. The influence of soil, drainage, and topography on corrosion rates is examined to determine representative corrosion growth rates along the pipeline. A systematic approach incorporating statistical analysis with mechanistic understanding of corrosion for preliminary corrosion assessment of pipeline systems is discussed.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it