MétaCan
Menu
Back to cohort
Record W2332196316 · doi:10.1190/segam2015-5899850.1

Frequent Seismic Monitoring for Pro-Active Reservoir Management

2015· article· en· W2332196316 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicReservoir Engineering and Simulation Methods
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceGeologyPetroleum engineering

Abstract

fetched live from OpenAlex

Summary Beyond exploration, the most important role for geophysics in the oil and gas industry is to influence field operations, so that the value of existing assets is fully realized. The recent trend in time-lapse seismic has been toward very frequent reservoir monitoring, with the aspiration to optimize both near- and long-term field management. In this paper we describe steps taken by Shell to tackle the main challenges of frequent seismic monitoring — cost, intrusiveness, and value realization. Offshore, cost reductions can be achieved through novel types of receivers and more efficient vessel utilization. Onshore, cost and footprint reductions are sought through novel survey designs, including fiber-optic DAS cables, sparse geometries, and movable subsurface sources. A demonstration of value is currently pursued through a large onshore trial of continuous monitoring of steam injection at Peace River, Canada, active since 2014. Initial results indicate that steam non-conformance can be diagnosed, remediation actions taken, and their effectiveness evaluated. Inter-disciplinary collaboration is a must. The associated workflow for assimilating frequent seismic data continues to develop and should benefit future monitoring projects both onshore and offshore.

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: Methods · Consensus signal: none
Teacher disagreement score0.521
Threshold uncertainty score0.505

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.073
GPT teacher head0.323
Teacher spread0.250 · 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