Modeling displacement flow inside a full-length casing string for well cementing
Bibliographic record
Abstract
While computer modeling of annular displacement efficiency is widely applied in cementing engineering, modeling the displacement flow inside a casing or drill string for cementing operations has received less attention. Although predicting displacement efficiency inside a full-length pipe is desired by cementing engineers, the attempt of developing a model with both efficiency and accuracy faces challenges. Access to computer simulators for this purpose is limited. Compared with annular flow, the displacement flow inside pipe, although within a simpler geometry and without eccentricity effect, is not simpler in physics, modelling strategy and predictability, because a variety of flow patterns and flow instabilities can develop to create complicated fluid interfaces. In this paper, we present an integrated numerical model developed to simulate displacement flows inside a full-length pipe, which connects an existing annulus model to enable complete displacement simulations of cementing jobs. The model uses three-dimensional grid to solve fluid concentrations with degrees of mixing, and incorporates flow instability detection and flow regime determination. Applied in cementing, the model accounts for effects of pumping rate, well inclination, pipe rotation, fluid densities, rheological parameters and more. This computationally efficient model does not rely on high-resolution mesh as often required by conventional Computational Fluid Dynamics models, thus it is suitable to be implemented in a cementing software for daily use by well cementing engineers. The methodology of the model is discussed in detail in this paper. To validate the model, we examine simulation results against experimental results obtained in our laboratory tests and CFD simulations; acceptable agreement is found under different testing conditions. We also presented two case studies of real cementing jobs with cement evaluation logs compared to simulation results, showing that the model can predict consistent displacement efficiency results.
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.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".