Transient Flow Assurance for Determination of Operational Control of Heavy Oil Pipelines
Bibliographic record
Abstract
Most liquid pipelines design and operational control is based on steady state flow analysis. This neglects dynamic effects that occur as a result of occurrence of surges in a pipeline caused by rapid changes in pressure as a consequence of changes in the flow rate. A transient analysis of liquid pipelines on the other hand assures pipeline performance under all conditions (steady state and dynamic situations) including evaluating the following: • Impact from pump station start up, delivery restriction or shutdown (zero delivery); • Pump unit trip/failure; • Rapid mainline valve closures including Slam shut of a non-return (check) valve; • Effect of running the pipeline with minimum flow and maximum pump discharge pressure operating condition; • Variation in demand including rapid reduction/curtailment of delivery volumes; • Bubble collapse (the transition from slack-line to tight-line flow); • Unintentional changes in operational position of control valves; • Fluid property delivery conditions; • Liquid injection assessment; • Surge protection including pressure relief/control system evaluation; • Restart requirement to avoid slack-line conditions prevalent in hilly/mountainous parts right of way (ROW). Such a dynamic analysis would indicate whether liquid surges are of concern from design, as well as system operational conditions. It also would provide an evaluation of an automated control or potential automated strategies for overpressure protection. In this paper the dynamic analysis of liquid pipelines resulting in design and operational benefits will be described. Finally their benefits in application to a heavy oil pipeline facilities “Keystone” will be highlighted.
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.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 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".