MétaCan
Menu
Back to cohort
Record W2071420920 · doi:10.2118/78996-ms

Automatic Determination of Well Placement Subject to Geostatistical and Economic Constraints

2002· article· en· W2071420920 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicReservoir Engineering and Simulation Methods
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsSimulated annealingMathematical optimizationComputer scienceComponent (thermodynamics)Context (archaeology)Reservoir modelingAlgorithmPetroleum engineeringMathematicsGeology

Abstract

fetched live from OpenAlex

Abstract Optimal well placement is a complex problem that requires detailed models of the reservoir structure/geometry and the petrophysical properties such as facies, porosity, permeability, and fluid saturation. The reservoir development team attempts to integrate all of these aspects when devising a well plan for optimal reservoir exploitation. Ideally the well locations would be selected with the assistance of a flow simulator; however, this is impractical due to time and CPU requirements. This paper presents a technique for selecting optimal well locations for fine-tuning with a flow simulator. The technique constructs the well placement problem as an optimization problem to be solved with simulated annealing. The global objective function consists of multiple component objective functions. Each component represents a desirable feature or constraint in the problem. Optimality is defined as the best balance among the component objectives. The format of the technique is flexible and can incorporate 3-D geostatistical models of uncertainty and multiple constraints. The proposed method iteratively refines initial well locations and trajectories until the global objective is maximized. Several examples are shown. Optimal well placement in a steam assisted gravity drainage context is illustrated.

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 categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.361
Threshold uncertainty score0.999

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.0010.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.016
GPT teacher head0.263
Teacher spread0.247 · 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