MétaCan
Menu
Back to cohort
Record W2005319786 · doi:10.2118/114991-ms

Tight Gas Production Performance Using Decline Curves

2008· article· en· W2005319786 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
KeywordsTight gasTransient (computer programming)Production (economics)Flow (mathematics)Work (physics)Petroleum engineeringTransient flowTransient analysisBilinear interpolationBoundary (topology)Work flowMechanicsEnvironmental scienceComputer scienceGeologyMathematicsEngineeringEconomicsTransient responseStatisticsIndustrial engineeringMechanical engineeringPhysicsMathematical analysis

Abstract

fetched live from OpenAlex

Abstract Traditional ("Arps") decline analysis is the most common reservoir engineering tool used for production performance forecasting. It has several advantages over other techniques in that it is simple to use, requires minimal data and is well understood by the industry. Currently, however, these methods are being misused in unconventional applications, such as tight gas. Production perfomance from tight gas reservoirs is characterized by steep initial decline rates and long periods of transient flow. If decline analysis is performed using this transient production data, the main assumption of boundary dominated flow (BDF) is violated and inaccurate forecasts may result. The goal of this work is to understand the behaviour of tight gas reservoirs during transient flow so that the familiar Arps method may be applied. The effects of different tight gas production responses (bilinear, linear, pseudo-radial, boundary dominated) are investigated. Finally, a methodology for applying traditional decline curve analysis to tight gas, with reference to long term transient flow, is presented.

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: Empirical · Consensus signal: Empirical
Teacher disagreement score0.022
Threshold uncertainty score0.315

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.046
GPT teacher head0.272
Teacher spread0.226 · 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