MétaCan
Menu
Back to cohort
Record W2030312535 · doi:10.2118/165285-ms

The Use of Modeling and Monitoring to Control Scale in Alberta ASP Floods

2013· article· en· W2030312535 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueSPE Enhanced Oil Recovery Conference · 2013
Typearticle
Languageen
FieldMaterials Science
TopicCalcium Carbonate Crystallization and Inhibition
Canadian institutionsHusky Energy (Canada)
Fundersnot available
KeywordsScale (ratio)Environmental scienceProduction (economics)Computer scienceGeography

Abstract

fetched live from OpenAlex

Abstract Two commercial Alkali Surfactant Polymer (ASP) floods became operational in the Taber area of Alberta, Canada in 2006 and 2008. Both of these floods used NaOH as the Alkali. Throughout the course of both projects extreme scale deposition was observed in downhole production equipment, gathering systems, and in the production facility.  Early in the life of the floods the scale composition was predominantly calcium carbonate, however over time the scale changed to consist of greater amounts of amorphous silicate. Scale inhibition and remediation strategies have been developed which include a comprehensive monitoring program, chemical scale inhibition, and mechanical scale prevention techniques. As a result of the large amount of data gathered, models were created to predict scale severity, content, and develop specific mitigation plans. Although clear field wide scaling trends can be identified over the life of these projects, scale mitigation strategies still need to be customized for each well. Although scale remains an operational challenge in these fields, with proper mitigation procedures it can be managed. This report documents the success in reducing the impact of the scale problem and slowing the depositional rate. When designing ASP floods it is important to plan for scale deposition and be proactive on scale mitigation.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.152
Threshold uncertainty score0.361

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.028
GPT teacher head0.241
Teacher spread0.213 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it