Evaluating the Impact of Wellbore Azimuth in the Marcellus Shale
Bibliographic record
Abstract
Abstract It is common industry knowledge that horizontal shale gas development is enhanced by drilling in the orientation parallel to the local minimum principal horizontal stress such that the induced hydraulic fractures grow parallel to the maximum horizontal stress during completion. Given the incongruous nature of mineral leases in the Marcellus Shale play, operators often drill in orientations that are sub parallel to this preferred azimuth in the interest of saturating acreage positions. What remains unknown is the degree to which this deviation from the preferred azimuth affects treatment pressures and/or more importantly well productivity. This case study will incorporate proprietary and public data in order to relate Marcellus well productivity to deviation from preferred horizontal well azimuth. In the effort to assess the impact horizontal wellbore azimuth bears on completions and well productivity, the productivity of wells in EQT’s core development areas has been correlated with the well’s deviation from minimum horizontal principal stress as determined from the analysis of over 25 image logs and cores across Pennsylvania and West Virginia. Furthermore, over 500 public domain wells released from the PA DEP and WV Geological Survey have been parsed and normalized to determine whether or not similar correlations can be made. The conclusions drawn from this study will determine if productivity is related to preferred wellbore azimuth and the regional variability of the relationship. Technical, logistical, and economic analysis will be applied to conclusions. This study has drawn some value from initial Marcellus public datasets that, while statistically significant in size, often lack in detail. The shortcomings of this large dataset will be normalized by the detailed datasets acquired from EQT’s core development areas. The ability to relate deviation from preferred wellbore azimuth to productivity will allow EQT and other operators to develop acreage more efficiently and optimize capital allocation.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".