A New Tool for Multi-Cluster & Multi-Well Hydraulic Fracture Modeling
Bibliographic record
Abstract
Abstract Unconventional gas and tight oil reservoirs require cost-effective fracturing technologies to optimize cost versus productivity and ensure viable commercial development. Horizontal wells together with completion techniques to initiate transverse fractures have been the key to unlocking these vast resources. Variables in the completion design for fracture stimulation in a horizontal well include injection rate, fluid properties, solid loading, well spacing, cluster spacing, and the sequence and timing of pumping stages between wells in a multi-well pad. An optimized design is critical to improve hydrocarbon production and to reduce the cost. However in current practice, multi-cluster and multi-well design is primarily based on progressive experience and is typically of standardized design in a given area (e.g. the clusters and wells are evenly distributed). This is due in part by the limitations of existing hydraulic fracturing simulators, including: 1. An assumption of planar fractures; 2. Fracture interference within and among stages and adjacent wells is ignored; and 3. Numerical instability when modeling systems with large dimensionless toughness e.g. slick water injection into high-toughness rock. This paper describes an emerging non-planar 3D fracturing software package with the capability to simulate interference between hydraulic fractures propagating from multiple clusters and multiple wells. Thus, both simultaneous and sequential multiple fracture propagation can be modeled. Furthermore, numerical instability with large dimensionless toughness is solved and makes it possible to predict the fracture geometry equally well for slick water fluids. The case study in this paper shows how fracture interference and proppant distribution occurs within a stage as well as between well and stages. The simulated fracture patterns can be matched with field microseismic data and the simulated pressure trend is in agreement with field operational data. Using this approach, multi-cluster and multi-well designs can be optimized in a manner not previously possible.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.003 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.024 | 0.003 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".