Pressure Barrier Applicability to Polymer Flood Design
Bibliographic record
Abstract
Abstract Effective oil displacement from a reservoir requires adequate and properly directed pressure gradients in areas of high oil saturation. If the polymer bank is too large or too viscous during a polymer flood, the pressure drop from the injection well to the polymer front may act as a pressure barrier by usurping most of the downstream driving force for oil displacement. Polymer injection pressures must be limited. The maximum allowable injection pressure is commonly constrained by caprock integrity, injection equipment, and/or regulations, even though fractures can be beneficial to polymer injectivity (and even sweep efficiency in some cases). This paper examines when the pressure-barrier concept limits the size and viscosity of the polymer bank during a polymer flood. Both analytical and numerical methods are used to address this issue. We examine the relevance of the pressure barrier concept for a wide variety of circumstances, including oil viscosities ranging from 10-cp (like at Daqing, China) to 1650-cp (like at Pelican Lake, Alberta), vertical wells (like at Tambaredjo, Suriname) versus horizontal wells (like at Milne Point, Alaska), single versus multiple layered reservoirs, permeability contrast, and with versus with crossflow between layers. We also examine the relation between the pressure-barrier concept and fractures and fracture extension during polymer injection. We demonstrate that in reservoirs with single layers, the pressure-barrier concept only limits the optimum viscosity of the injected polymer if the mobility of the polymer bank is less than the mobility of the displaced oil bank. The same is true for multi-zoned reservoirs with no crossflow between layers. Thus, for these cases, the optimum polymer viscosity is likely to be dictated by the mobility of the oil bank, unless other factors (like fracture extension) intervene. For multi-zoned reservoirs with free crossflow between layers, the situation is different. A compromise must be reached between injected polymer viscosity and the efficiency of oil recovery. The relevance of our findings is applied to operations for several existing polymer floods. This work is particularly relevant to viscous-oil reservoirs (like Pelican Lake and others) where the injected polymer viscosities are substantially lower than the oil viscosity
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.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| 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".