Can Large Domain of Uncertainty Be Reduced for Two One-Well Fault Blocks?
Bibliographic record
Abstract
Abstract Two fault blocks, each containing one producing well, are part of a multiparty concession. Both blocks were tested by a major oil company in the mid 80's but proved to be non-commercial at that time and the wells were abandoned. Two further wells were drilled in early '01 and late '03 and have been on production since then. The short production history is common today for many companies pursuing marginal oil accumulations. Recent high oil prices have enabled viable production but the degree of uncertainty makes it difficult to diagnose reservoir performance and identify the best alternatives for future reservoir development. The producing mechanism for the two fault blocks is believed to be depletion drive. However, high dip with some evidence of fracturing indicates possible improved recovery via gravity drainage. Material balance calculations utilizing limited production history, few pressure measurements and uncertain PVT data make it difficult to resolve OOIP, prevailing drive mechanisms, and ultimate recovery. The BPP is also uncertain which consequently affects material balance.Accurate PVT data will give confidence in resolving the issue of whether a fault separating the two blocks is leaking.This fault is thought to be partially non-sealing as indicated by few uncertain pressure measurements, which complicate interpretations and decisions regarding further development. The offshore location limits artificial lift or secondary recovery options. Production capacity is allotted from a shared facility and future decisions will require agreement among the involved parties. These concerns, in addition to considerable G & G unknowns regarding seismic definition of structure, facies variation, poroperm characteristics etc., generate a large domain of uncertainty. This is exacerbated by the interests and visions of the different partners and local regulations. The best solution starts by an interdisciplinary team approach to enhance the understanding and potential impact of all available data through expert analysis and thoughtful integration. This results in more effective decisions regarding reservoir management and further development. PVT acquisition, multiphase metering, static modeling, reservoir simulation and infill drilling are some steps of an aggressive plan to develop this Concession.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.014 | 0.076 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.003 | 0.006 |
| Open science | 0.003 | 0.003 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".