MétaCan
Menu
Back to cohort
Record W2091462331 · doi:10.1115/ipc2010-31157

A Study of Cases of Hydrostatic Tests Where Multiple Test Failures Have Occurred

2010· article· en· W2091462331 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

Venue2010 8th International Pipeline Conference, Volume 1 · 2010
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsTransCanada (Canada)
Fundersnot available
KeywordsHydrostatic testReliability engineeringIntegrity managementPipeline (software)Pipeline transportHydrostatic pressureTest (biology)Computer scienceEngineeringStructural engineeringGeologyMechanical engineering

Abstract

fetched live from OpenAlex

The retesting of pipelines for integrity management purposes often involves testing of pipelines where multiple test failures can be expected. Multiple failures are most likely to occur when an existing pipeline is tested to a hoop stress level in excess of those used in prior tests of the pipeline. A major cause of such failures is seam manufacturing defects, but other types of defects such as mechanical damage or stress corrosion cracking may cause numerous failures as well. The occurrence of multiple failures can be costly in terms of the time the pipeline must remain out of service. Multiple failures sometimes involve pressure reversals that may affect confidence in the level of integrity sought by the pipeline operator. The study described in this paper involved a review of five actual cases of hydrostatic tests where multiple test failures occurred. On the basis of these cases a method was developed for predicting the ultimate number of failures required to reach a desired test level from the pressure levels of the first few failures. In addition, an improved method for estimating the probability of a pressure reversal of a given size was developed. Pipeline operators could use these techniques to decide when to terminate a hydrostatic test and to assess the effectiveness of the test in terms of a level of confidence that an integrity-threatening pressure reversal will not 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 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.834
Threshold uncertainty score0.999

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.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0020.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.021
GPT teacher head0.267
Teacher spread0.246 · 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