Simulating In-Service Welding of Hot-Tap Branches to Quantify the Effect of Geometry on Level of Restraint
Bibliographic record
Abstract
Economic and environmental incentives encourage operators to maintain pipeline operation during repair and maintenance procedures including hot-tap branch fitting installation onto pipelines. Welding onto a liquid-filled pipeline induces accelerated cooling of the weld and heat affected zone (HAZ), increasing the propensity for cracking. In-service welding codes and due diligence requires that several key factors be considered during the design of an in-service welding procedure specification for its intended purpose. The level of restraint (LoR) imposed by the geometry, material, or dimensional differences of the branch compared to the run pipe has also been shown to be a significant contributor to cracking. Finite element analysis (FEA) was utilized to investigate the geometric effects of an in-service weld procedure to approximate the LoR of hot-tap branch installation. The LoR was quantified and compared by simulating multi-pass weld sequences on two configurations: a branch-on-pipe (BoP) configuration of various dimensions and a configuration using perpendicular plates (PP) that has been used as an alternative to the branch-on-pipe configuration. The highest LoR, as measured by transverse tensile stress at the fillet weld toe, was the branch-on-pipe configuration with the largest branch wall thickness, the smallest branch diameter, the largest run pipe diameter, and the largest run pipe wall thickness. FEA modeling revealed that the PP configuration has lower LoR, thus it is not recommended to use for simulating in-service branch weld procedures.
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.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.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.005 | 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 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".