Methodology for Estimating Recovered Solvent in Solvent-Aided Process
Bibliographic record
Abstract
Summary The solvent-aided process (SAP) is a solvent-based enhancement of steam-assisted gravity drainage (SAGD) in which small amounts of solvent, such as light alkanes or natural-gas liquids, are added to the injected steam to enhance reservoir performance and associated project economics. Expectedly, the economics with SAP are sensitive to the solvent recovered from the reservoir, making its measurement in a field test an important factor. When a single-component solvent such as butane, which is not generally present in the produced heavy oil or bitumen, is used in SAP, estimation of the recovered solvent can be achieved uniquely. But when the solvent also has heavier components, some of which overlap with the lighter components of the produced oil, the measurement is not straightforward. The problem is compounded by the fact that the interaction with the reservoir changes the composition of the produced solvent and makes it time variant on account of different resident times associated with different components. The issue is further complicated by the fact that produced oil also undergoes an in-situ solvent deasphalting process (SDA), which is also time and space variant in the reservoir. If there were no in-situ SDA, one potential method to measure the amount of produced solvent would be to measure the total asphaltene content as an oil "marker" in the produced blend. Use of a tracer with injected solvent, as well as regression-based analyses for solvent fraction (using compositional analyses of solvent, bitumen, and the blend) of the produced blend, is error prone for these same reasons. Because of the issues in these approaches, a new method is desirable for a more-robust and unique assessment of the solvent amount in the produced fluids. This paper elaborates on the current challenges and proposes a couple of workable methods, including use of maltenes/metals content as oil markers as well as the use of boiling-point curves of the produced blend compared with the boiling point of the base oil. Such techniques of estimating the recovered solvent can facilitate a more-objective assessment of SAP field tests and enable economic evaluation of SAP application to a commercial scale.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.003 |
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".