MétaCan
Menu
Back to cohort
Record W2022162726 · doi:10.2118/06-04-das

What in the Reservoir is Geostatistics Good For?

2006· article· en· W2022162726 on OpenAlexaff
Clayton V. Deutsch

Bibliographic record

VenueJournal of Canadian Petroleum Technology · 2006
Typearticle
Languageen
FieldEngineering
TopicReservoir Engineering and Simulation Methods
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsGeostatisticsReservoir modelingReservoir engineeringComputer scienceSet (abstract data type)Data miningGeologyPetroleum engineeringSpatial variabilityMathematicsStatistics

Abstract

fetched live from OpenAlex

Abstract Geostatistics provokes strong reactions. There are champions who believe the application of geostatistics adds value in almost any reservoir modelling situation. There are skeptics who do not think that a geostatistical model will have a meaningful impact on reservoir management decisions. The majority of engineers and geoscientists, however, are seeing an increasing use of geostatistics and are not sure when geostatistics should be used and how the results affect reservoir decisions. There are three specific cases where geostatistics can provide valuable support for decision-making:calculating maps of uncertainty over large areas to support resource calculations and well placement;reconciling well and seismic data into high resolution reservoir models; and,constructing representative models of heterogeneity to provide input to flow simulation and support reservoir forecasting. These three cases are developed without excessive theoretical detail. Realistic examples are presented without getting lost in the details of a particular reservoir. Limitations and pitfalls are discussed. Framework of Geostatistics Geostatistics refers to the theory of regionalized variables and the related techniques that are used to predict variables such as rock properties at unsampled locations. Matheron formalized this theory in the early 1960s(1). Geostatistics was not developed as a theory in search of practical problems. On the contrary, development was driven by engineers and geologists faced with real problems. They were searching for a consistent set of numerical tools that would help them address real problems such as ore reserve estimation, reservoir performance forecasting, and environmental site characterization. Reasons for seeking such comprehensive technology included:an increasing number of data to deal with;a greater diversity of available data at different scales and levels of precision;a need to address problems with consistent and reproducible methods;a belief that improved numerical models should be possible by exploiting computational and mathematical developments in related scientific disciplines; and,a belief that more responsible decisions would be made with improved numerical models. These reasons explain the continued expansion of the theory and practice of geostatistics. Problems in mining, such as unbiased estimation of recoverable reserves, initially drove the development of geostatistics. Problems in petroleum, such as realistic heterogeneity models for unbiased flow predictions, were dominant from the mid 1980s through the late 1990s. More recently, the problems of realistic geologic modelling and reliable uncertainty quantification are driving development. The main focus of geostatistics is constructing high-resolution 3D models of categorical variables, such as facies, and continuous variables, such as porosity and permeability. It is necessary to have hard truth measurements at some volumetric scale. All other data types including geophysical data are considered soft data and must be calibrated to the hard data. It is neither possible nor optimal to construct models at the resolution of the hard data. Models are generated at some intermediate geological modelling scale, and then scaled to an even coarser resolution for resource calculation or flow simulation.

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 imitation

Not 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.

metaresearch head score (Codex)0.025
metaresearch head score (Gemma)0.064
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.025
Threshold uncertainty score0.131

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0250.064
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0050.007
Science and technology studies0.0040.019
Scholarly communication0.0140.021
Open science0.0020.003
Research integrity0.0050.007
Insufficient payload (model declined to judge)0.0070.003

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.012
GPT teacher head0.246
Teacher spread0.234 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreEmpirical

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".

Quick stats

Citations10
Published2006
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Canadian Petroleum TechnologySame topicReservoir Engineering and Simulation MethodsFrench-language works237,207