Feasibility of In-Situ Combustion in the SAGD Chamber
Bibliographic record
Abstract
Summary Steam-assisted gravity drainage (SAGD) is a commercially successful bitumen-recovery method that has transformed some of the vast Canadian oil-sand deposits into recoverable reserves. Several SAGD projects have been developed in northern Alberta in the past few years, and many more are in the planning stages. As the projects mature, new operational problems are revealed, demanding new solutions. Because of operational restrictions, it is almost impossible to have the same growth rate in all steam chambers in a SAGD pattern. Hence, interference between a mature chamber and an adjoining immature chamber can become a problem. Steam leakage from the immature chamber into the mature chamber reduces the thermal efficiency of the project and requires a solution to prevent the steam dissipation. Filling the mature chamber with combustion gases is a possible solution for this problem. Carrying out in-situ combustion (ISC) in the mature chamber not only would create the needed combustion gases in the chamber, but also could recover a substantial part of the residual oil in the mature chamber. It is also likely that the combustion would create a reduced-permeability coke (toluene insoluble fraction) zone around the mature chamber, thus isolating it from the rest of the reservoir. To evaluate the merit of this idea, an elevated-pressure experiment was conducted using a 2D physical model. The conventional SAGD process was conducted in the model to develop a steam chamber. Air was then injected through a horizontal well near the top of the model into the SAGD chamber, and a combustion front was established around the air-injection well. By operating combustion in the depleted chamber, residual oil was mobilized and produced. Additional oil recovery was attained by more than 20% over the SAGD operation as a bonus. Initiation and propagation of combustion were confirmed by a large increase in the temperature in the combustion zone. After unpacking the model, it was found that a coke layer formed around the perimeter of the chamber.
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.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".