MétaCan
Menu
Back to cohort
Record W2009619446 · doi:10.2118/169062-ms

A Survey of Polymer Flooding in Western Canada

2014· article· en· W2009619446 on OpenAlex
G. Renouf

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.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueSPE Improved Oil Recovery Symposium · 2014
Typearticle
Languageen
FieldEngineering
TopicEnhanced Oil Recovery Techniques
Canadian institutionsSaskatchewan Research Council (Canada)
FundersPetroleum Technology Research Centre
KeywordsFlooding (psychology)Petroleum engineeringEnhanced oil recoveryEnvironmental scienceInclusion (mineral)GeologyMineralogy

Abstract

fetched live from OpenAlex

Abstract Polymer flooding is becoming increasingly more common and more successful in western Canada. In the year 2011, western Canada produced over 1,600,000 m3 of oil using polymer flooding. In the statistical study reported here, production, injection, reservoir, and operating data were gathered from 32 polymer floods of heavy and medium oil in western Canada. Success was highly variable. Incremental recovery ranged from 0.5 to 14% of the original oil in place over periods lasting between 1 and 9 years. Half of the polymer floods in the project showed a decline in water cut. Oils of very high viscosity and low gravity—as high as 5,000 mPa-s for dead oil and as low as 15°API gravity — were successfully flooded using a polymer solution. Operational factors that were most significant to flooding success were injection volumes and rates; inclusion of horizontal wells, in particular injection wells; and water quality. Water quality was a major issue, suggesting that the success of many projects comes down to handling operational issues rather than project concept or design. Polymer integrity and injectivity led to many of the operational difficulties.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
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.435
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.006
GPT teacher head0.200
Teacher spread0.194 · 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