Hydrotest Protocol for Applications Involving Lower-Toughness Steels
Bibliographic record
Abstract
Hydrotesting has been used by the transmission pipeline industry for decades, and remains the only effective means to control stress-corrosion cracking until in-line inspection is proven. This paper addresses the conditions for effective proof-pressure testing in terms of ductile fracture referenced to peak pressure and hold-time, and then contrasts these to the response in low-toughness situations. Fracture properties typical of an early-vintage electrical-resistance weld (ERW) seam were determined and used as the basis to simulate the response at toughness levels typical of some lower-toughness steels. Fracture properties characterized via Charpy-vee notch (CVN) energy showed low energy to failure, and confined inelastic response characteristic of linear-elastic fracture mechanics. Hydrotest and service breaks associated with cracking in an ERW seam showed a very small shear lip and often showed chevrons pointing back toward the origins — features consistent with the CVN results and characteristic of low fracture ductility. The results indicate hydrotest protocols derived and effective for ductile fracture are not directly applicable when brittle-like fracture controls. Hydrotesting was indicated to be an effective means to expose defects in ERW seams, as rupture is indicated to occur under typical hydrotest conditions. Simulated growth of the scope of defect lengths and depths evident along hydrotest breaks showed virtually no time dependent cracking, which means the hold time at maximum pressure should be reduced to the minimum time required to ensure all pipe in the test section has reached its target pressure.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| 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.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.009 | 0.002 |
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 itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".