Limited Height Growth and Reduced Opening of Hydraulic Fractures due to Fracture Offsets: An XFEM Application
Bibliographic record
Abstract
Abstract Hydraulic fracture propagation through a layered medium often exhibits a complex fracture path due to lateral shifting of the fracture path after passing through an interface. The existence of these offsets in the fracture path has been confirmed by mapping of mined fractures and by laboratory experiments. In addition to the stress contrast and material contrast, these offsets act as another mechanism for fracture-height containment. In order to investigate fracture height growth problem, we have considered a case of plane-strain fractures propagating from an injection point and propagating in a predetermined path. Fracture offsets of a given length and angle are prescribed within the predetermined path. In this way, we parametrize the problem of fracture offsets in order to quantify their effects on the fracture height growth and fracture opening reduction at the fracture offset (pinching effect). This is done while keeping a hydrostatic state of confining stresses in order to observe only the geometric effect of the fracture offset. We use a recently developed hydraulic fracturing code based on the eXtended Finite Element Method (XFEM). This code solves the fluid flow in the fracture and the elastic response of the fracture in a fully coupled manner solving for the fracture velocity using the complete hydraulic fracture tip asymptotics. For different combinations of independent parameters (i.e., formation moduli, far-field stresses, fluid injection rate, ratio of offset length to the length of the straight fracture and the offset angles) we investigate the effect on the fracture height growth and the reduction in fracture opening at the fracture offset. A detailed parametric study shows that while each parameter affects the fracture height containment, the fracture opening reduction is dominated by the fracture offset angle which is a geometric effect of the fracture offsets. This has a profound effect on the proppant bridging at the fracture offset.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
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".