Bibliographic record
Abstract
In North America’s most active shale fields, the drilling and hydraulic fracturing of new wells is directly placing older adjacent wells at risk of suffering a premature decline in oil and gas production. The underlying issue has been coined as a “frac hit.” And though they have long been a known side effect of hydraulic fracturing, frac hits have never mattered or occurred as much as they have recently, according to several shale experts who say the main culprit is infill drilling. “It is a very common occurrence—almost to the point where it is a routinely expected part of the operations,” said Bob Barree, an industry consultant and president of Colorado-based petroleum engineering firm Barree & Associates. He added that frac hits are also an expensive problem that involve costly downtime to prepare for, remediation efforts after the fact, and lost productivity in the older wells on a pad site. A frac hit is typically described as an interwell communication event where an offset well, often termed a parent well in this setting, is affected by the pumping of a hydraulic fracturing treatment in a new well, called the child well. As the name suggests, frac hits can be a violent affair as they are known to be strong enough to damage production tubing, casing, and even wellheads. Claudio Virues, a senior reservoir engineer with CNOOC Nexen, said frac hits have become a top concern in the shale business because they can affect several wells on a pad, along with those on nearby pads too. Based on his experiences in Canada and in south Texas, the question is no longer if a frac hit will happen, but how bad will it be. “You usually have two scenarios,” he said. “One may be that you have a temporary loss of production, but you will recover to the trend that you had before. The other will be really bad for your production and reserves.” He is alluding to the fact that some wells impacted by frac hits never fully recover and, in the worst cases, permanently stop producing after taking frac hits. The frequency of these outcomes are unknown as there are no publicly available statistics. In a small minority of cases, and in select formation types, frac hits have been known to increase production in the impacted well, but this is unusual.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.008 | 0.002 |
| Scholarly communication | 0.006 | 0.005 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.006 | 0.003 |
| Insufficient payload (model declined to judge) | 0.032 | 0.010 |
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".