MétaCan
Menu
Back to cohort
Record W2324501766 · doi:10.2118/170011-ms

How Does the Incorporation of Engineering Knowledge Using Fuzzy Logic during History Matching Impact Reservoir Performance Prediction?

2014· article· en· W2324501766 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.

Bibliographic record

VenueSPE Heavy Oil Conference-Canada · 2014
Typearticle
Languageen
FieldEngineering
TopicReservoir Engineering and Simulation Methods
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsMatching (statistics)Computer scienceFuzzy logicWorkflowData miningPopulationIndustrial engineeringMachine learningArtificial intelligenceEngineeringMathematicsStatisticsDatabase

Abstract

fetched live from OpenAlex

Abstract Population-based optimization algorithms are shown to be excellent candidates for improving the speed and solution diversity of history matching and optimization workflows, based on their successful track records for solving real-world problems. The incorporation of reservoir engineering knowledge within these workflows, however, has been somewhat neglected. In particular, there is a lack of capability for guiding the optimization algorithms to specific regions of the search space. In a previous study, we introduced a framework for helping reservoir engineers incorporate their knowledge into history matching and optimization frameworks, by coupling a rule-based fuzzy system with a population-based sampling method. The question is how the use of this type of information in history matching affects the performance of the reservoir study during the prediction stage. This paper investigates the effect that the incorporation of reservoir engineering knowledge during the history matching of the Teal South model production data has on reservoir performance in the prediction stage. Two scenarios are considered. In Case I, we augment the history matching with reservoir engineering knowledge and then produce a forecast. In Case II, production data is history matched using differential evolution (DE), without fuzzy-logic-based engineering knowledge, then a forecast is produced The results show that incorporating engineering knowledge of the reservoir under study during the history matching process can significantly reduce the uncertainty in the forecast, compared with the case where unrealistic parameter value ranges are used.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.155
Threshold uncertainty score0.830

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.026
GPT teacher head0.230
Teacher spread0.204 · 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