Interfacial Stability and Displacement Efficiency in Thermal Solvent Processes
Bibliographic record
Abstract
Abstract Expanding-Solvent Steam-Assisted Gravity Drainage (ES-SAGD) and Solvent-Assisted Cyclic Steam Stimulation (SA-CSS) are in situ steam-solvent recovery process to produce heavy oil and bitumen reservoirs. In ES-SAGD and SA-CSS, steam and solvent are injected into the depletion chamber within the reservoir. At the chamber edge, the steam releases its latent heat heating the oil there and solvent mixes with mobilized bitumen which then flows under gravity to the lower horizontal producer. There are many factors that influence the efficiency and rate at which oil is mobilized. One of them is the stability of the steam-oil interface which is controlled by the concentration and temperature dependencies of viscosity and density and the relative magnitudes of viscous, gravity (buoyancy), and capillary forces. In this research, the stability of the chamber interface between the vapour chamber and the bitumen at the edge of the chamber is examined. We present theoretical evidence for occurrence of such instability and conditions at which the interface is unstable. The results demonstrate that steam-solvent injection enhances the instability of the interface thus promoting greater mixing at the edge of the chamber. Consequently, the oil rate of a steam-solvent process is higher than that of a steam-only one. Therefore, there are three fundamental contributions to enhanced production by solvent-steam processes: first, the oil phase viscosity is lowered, second, the oil saturation is enhanced at the edge of the chamber, and third, the vapour-oil interface becomes more unstable which promotes more mixing at the chamber edge. The stability of the interface is also controlled by the balance between the solvent's solubility in the oil phase and the ability of the solvent to reduce the viscosity of the oil phase. The results of the stability analysis confirm the findings of laboratory experiments and field tests which demonstrate that processes that use solvent+steam yield higher production rates than that of steam alone.
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.001 |
| 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.000 | 0.000 |
| Research integrity | 0.000 | 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".