MétaCan
Menu
Back to cohort
Record W2560220346 · doi:10.2118/184157-ms

Maximizing VOI of Frequent Seismic Monitoring of Heavy Oil Fields: Case Study at Peace River Pad 31

2016· article· en· W2560220346 on OpenAlex
J. K. Przybysz-Jarnut, J. H. H. M. Potters, Jorge López, M. Araujo

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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueSPE Heavy Oil Conference and Exhibition · 2016
Typearticle
Languageen
FieldEngineering
TopicOil and Gas Production Techniques
Canadian institutionsnot available
Fundersnot available
KeywordsEnvironmental scienceOil fieldOil productionPetroleum engineeringComputer scienceGeology

Abstract

fetched live from OpenAlex

Abstract In May 2014 a permanent seismic monitoring system was deployed in Peace River Pad 31 to monitor areal steam conformance during pad re-development in this heavy oil field in Alberta, Canada. The dataset comprises a two-year monitoring period and was used within the Well and Reservoir Management framework to optimize production performance and increase field recovery. With seismic snapshots available daily, one area of investigation was to determine the monitoring frequency that maximizes Value of Information (VOI). A lookback study with a panel of independent experts showed that for the particular case of Pad 31, with very limited control due to the existing well completions, quarterly monitoring would be sufficient. Additionally, guidelines were developed for defining an effective seismic monitoring program (e.g., align monitoring with major field interventions, allow enough time for changes to be actionable, etc.). Although based on observations from the Pad 31 trial, these guidelines should be applicable to other thermal developments in heavy oil fields.

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.891
Threshold uncertainty score0.536

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.250
Teacher spread0.222 · 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