MétaCan
Menu
Back to cohort
Record W1992999167 · doi:10.2118/162661-ms

Flowback Analysis for Fracture Characterization

2012· article· en· W1992999167 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

VenueSPE Canadian Unconventional Resources Conference · 2012
Typearticle
Languageen
FieldEngineering
TopicHydraulic Fracturing and Reservoir Analysis
Canadian institutionsAlberta LibraryUniversity of Alberta
Fundersnot available
KeywordsHydraulic fracturingPetroleum engineeringFracture (geology)GeologyPermeability (electromagnetism)Fracturing fluidReservoir modelingGeotechnical engineeringChemistry

Abstract

fetched live from OpenAlex

Abstract Tight reservoirs stimulated by multistage hydraulic fracturing are commonly characterized by analyzing the hydrocarbon production data. However, analyzing the available hydrocarbon production data mainly determines the fracture-matrix interface. This analysis is not enough for a full characterization of the induced hydraulic fractures. Before putting the well on flowback, the induced fractures are occupied by the compressed fracturing fluid. Therefore, analyzing the produced fracturing fluid should in principle be able to characterize the induced fractures, and complement the production data analysis. We develop a rate transient model for describing the fracturing fluid flowback. We also make various diagnostic plots for understanding the flowback behavior of three fractured horizontal wells. The diagnostic plots indicate three separate flowback regions. In the first region, water production dominates while in the third region hydrocarbon production dominates. In the second region, water production drops and hydrocarbon production ramps up. In general, we observe a linear relationship between rate normalized pressure (RNP) and material balance time (MBT) for the three regions. However, the proposed model can only describe the response of the first region. We successfully determine the hydraulic fracture permeability by history matching the early time flowback data. We conclude that the flowback analysis can complement the production data analysis for a comprehensive fracture characterization. The presented study encourages the industry to start careful measurement of the rate and pressure data immediately after putting the well on hydraulic fracture flowback.

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.769
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.0020.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.014
GPT teacher head0.214
Teacher spread0.200 · 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