What Is the Leak Rate for a Liquid Slug Flowing Past a Side Branch?
Bibliographic record
Abstract
Abstract Chemical cleaning is used in gas pipelines to remove debris that was resistant to mechanical cleaning. The cleaner is a liquid mixture of a hydrocarbon-based solvent and a surfactant. It is transported down the pipeline either batched between two cleaning tools or pushed by a single tool. During a chemical cleaning run, liquid will leak into any side branch it passes. Consequently, gas quality problems may arise when the pipeline returns to regular operations as the leaked liquid hydrocarbons evaporate into the gas stream. Furthermore, operational problems such as flooded separators can occur if a large volume of liquid is lost. Currently, there is no understanding of what factors influence the liquid’s leak rate into side branches. This paper aspires to address this knowledge gap. A water flow loop was set up to investigate the effect on leak rate of mainline pipe size, side branch pipe size, side branch length, and mainline liquid velocity. The leak rate is found to increase with the side branch pipe size, while remaining unaffected by the mainline pipe size and side branch length. At mainline velocities below the critical velocity, gravitational effects such as the downstream back pressure significantly affect the leak rate. At mainline velocities above the critical velocity these effects disappear, and the leak rate decreases as the mainline liquid velocity increases.
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.002 | 0.008 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".