Integrated One-Step Process for Oil Water Separation and Produced-Water Treatment
Bibliographic record
Abstract
Abstract Facilities for steam-assisted gravity drainage (SAGD) require vessels for oil/water emulsion separation, water treatment, and steam generation. Gravity separation is generally used to separate emulsion, with the requirement of diluent and a demulsifier chemical addition. Treatment of emulsion and water constitute a major capital component and operating cost, and generally involves skim tanks, gas flotation, filtration, warm lime softening, and ion exchange. Most facilities use once-through steam generators (OTSGs) to generate steam because of their ability to handle water with a higher concentration of dissolved solids relative to package boilers. Heins and Peterson suggested an alternative method for water treatment utilizing a vertical tube falling film evaporator (Heins and Peterson 2003). Water vapour is compressed, raising its temperature, and transfers its latent heat to the untreated water. The condensed water is recovered as high quality distillate and the vapour is recirculated. Benefits of this process include reduced water treatment costs and increased boiler feed water quality, allowing for use of package boilers instead of OTSGs and reduced liquid discharge requiring disposal. The authors propose an extension of the evaporative water treatment process whereby the evaporator acts as both a water purification and emulsion separation unit. This process can be retrofitted to current SAGD operations and, in addition to the benefits of evaporative water treatment, can reduce or eliminate the need for diluent and chemical addition for emulsion separation.
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.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
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".