MétaCan
Menu
Back to cohort
Record W3035812168 · doi:10.1190/int-2019-0294.1

Seismic reservoir characterization of Bone Spring and Wolfcamp Formations in the Delaware Basin — A case study: Part 1

2020· article· en· W3035812168 on OpenAlex
Satinder Chopra, Ritesh Kumar Sharma, James Keay

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

VenueInterpretation · 2020
Typearticle
Languageen
FieldEarth and Planetary Sciences
TopicSeismic Imaging and Inversion Techniques
Canadian institutionsTrusted Positioning (Canada)
Fundersnot available
KeywordsInversion (geology)Structural basinGeologySeismic inversionReservoir modelingHydrocarbon explorationSeismologyPetroleum engineeringPaleontology

Abstract

fetched live from OpenAlex

The Delaware and Midland Basins are multistacked plays with production being drawn from different zones. Of the various prospective zones in the Delaware Basin, the Bone Spring and Wolfcamp Formations are the most productive and thus are the most drilled zones. To understand the reservoirs of interest and identify the hydrocarbon sweet spots, a 3D seismic inversion project was undertaken in the northern part of the Delaware Basin in 2018. We have examined the reservoir characterization exercise for this dataset in two parts. In addition to a brief description of the geology, we evaluate the challenges faced in performing seismic inversion for characterizing multistacked plays. The key elements that lend confidence in seismic inversion and the quantitative predictions made therefrom are well-to-seismic ties, proper data conditioning, robust initial models, and adequate parameterization of inversion analysis. We examine the limitations of a conventional approach associated with these individual steps and determine how to overcome them. Later work will first elaborate on the uncertainties associated with input parameters required for executing rock-physics analysis and then evaluate the proposed robust statistical approach for defining the different lithofacies.

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

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.022
GPT teacher head0.237
Teacher spread0.215 · 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