Dynamic Fracture Modelling Approach for Cold Lake Cyclic Steam Stimulation
Bibliographic record
Abstract
Abstract In Imperial Oil’s Cold Lake field, Cyclic Steam Stimulation (CSS) is used to recover bitumen from the Clearwater formation. At initial reservoir conditions, fluids are essentially immobile due to high bitumen viscosity and due to very low relative permeability to water. The injection of steam is achieved by injecting at pressures that induce hydraulic fractures in the formation. Numerical simulation techniques typically handle fracturing by imposing a large increase in permeability as the pressure exceeds a fracture pressure. Standard simulation approaches using an ExxonMobil in-house simulatori to modeling fracturing require an excessive pressure gradient in order to propagate a fracture. As a result, the pressure of the fracture blocks is overestimated, resulting in an unrealistic overestimate of leak-off from the fracture. The fracture area is thereby significantly underestimated and possible fluid communication between wells is not properly modeled. The term "dynamic fracturing" refers to an approach that improves hydraulic fracture modeling by using a variation of upstream weighting to calculate the effective permeability between fracture blocks. The upstream weighting is done indirectly using changes in void ratio, which is a measure of pore dilation due to pressure change. The method has been calibrated with field data from two Cold Lake pads. Early attempts to use this method encountered numerical stability problems. This resulted in very slow run times, and in many instances, cases could not be completed. The method has been improved using a simple dampening scheme making it practical to use in multi-well models. This approach is aimed at improving predictions of fluid distribution in early cycles of CSS including predictions for infill well performance. More realistic fluid communication modeling improves subsequent infill performance predictions. Useful comparisons of performance from different steam strategies require good predictions of fluid distribution caused by each strategy. This work has imporved our ability to model the CSS process and to predict field behaviour.
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 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".