Mechanics and Up-Scaling of Heavy Oil Bitumen Recovery by Steam-Over-Solvent Injection in Fractured Reservoirs (SOS-FR) Method
Bibliographic record
Abstract
Abstract Recently, the steam-over-solvent injection in fractured reservoirs (SOS-FR) method was proposed as a potential solution for efficient heavy-oil/bitumen recovery in oil-wet naturally fractured reservoirs. The method is based on initial injection steam (Phase-1), followed by solvent (Phase-2). In the third cycle (Phase-3), steam is injected again to recover more oil and retrieve the solvent. Solvent retrieval during the third cycle was observed to be very fast if the temperature is around the boiling point of the solvent. This process is controlled by efficient matrix recovery and the mechanics of the process needs to be clarified to further determine the efficient application conditions for the given matrix and oil characteristics. Single matrix behavior during the process was numerically modeled for static conditions and the results were matched with the experimental observations. The physics of the recovery mechanism was analyzed through visual inspection of saturation and concentration profiles in each cycle. The major observation was the substantial effect of gravity in oil recovery when the matrix was exposed to solvent. Special attention was given to the solvent retrieval rate and amount in Phase-3 and the permeability reduction due to asphaltene precipitation in Phase-2. This phenomenon was modeled using a permeability function changing with spatial coordinates and time, i.e. k=f(x, y, z, t). It was observed that permeability reduction due to asphaltene precipitation is significant and needs to be taken into account in modeling the process. After showing the effect of the matrix size on the oil recovery and solvent retrieval, an up-scaling analysis was performed. The log-log relationship between the time value to reach ultimate recovery and the matrix size yielded a straight line relationship with a non-integer exponent less than two for all three phases of the process. The observed straight line relationship (and the exponent values obtained) is highly encouraging to extend the study to obtain a universal scaling relationship.
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.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".