MétaCan
Menu
Back to cohort
Record W1964233866 · doi:10.2118/140105-ms

Utilizing Fluid and Proppant Tracer Results to Analyze Multi-Fractured Well Flow Back in Shales: A Framework for Optimizing Fracture Design and Application

2011· article· en· W1964233866 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 Hydraulic Fracturing Technology Conference · 2011
Typearticle
Languageen
FieldEngineering
TopicHydraulic Fracturing and Reservoir Analysis
Canadian institutionsOncolytics Biotech (Canada)Apache (Canada)
Fundersnot available
KeywordsTRACERMicroseismFracture (geology)Oil shaleFlow (mathematics)Petroleum engineeringFluid dynamicsFracturing fluidGeologyStage (stratigraphy)Volumetric flow rateConductivityGeotechnical engineeringMechanicsPhysicsSeismology

Abstract

fetched live from OpenAlex

Abstract Fluid and proppant tracers and other simple measurements in returning load water flow back can be very useful in helping to describe fracture development in shales; including such parameters as fracture complexity, frac conductivity, height growth, frac barrier effectiveness, well-to-well and frac-to-frac interference, water entry points and general fracturing execution. For most engineers, flow back ion charts have often had little relevance beyond estimating frac stage flow back activity; however, combining fluid tracer information with low-level gamma emitting proppant tracers, microseismic, simple salinity measurements and water return rate can help describe fracture and formation behaviors that lead to faster optimization of fracturing design and application. This paper will use fluid and proppant tracer results from over a hundred shale frac stages in horizontal wells along with other measurements of frac flow back and blend them with microseismic, frac pumping records, production logging and production results to build a framework for better analysis of frac flow back.

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.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
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.600
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0010.001
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.028
GPT teacher head0.251
Teacher spread0.223 · 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