Field Application of New Lightweight Proppant in Appalachian Tight Gas Sandstones
Bibliographic record
Abstract
Abstract Stimulation treatment designs must provide a delicate balance between completion effectiveness and economical viability. Service company research and development dollars have historically been spent to find the most cost effective treatment fluid for tight, gas-bearing zones. Typically, the focus of this research has been on fracturing fluids and viscous fluid proppant transport. Thin banking fluids have been proven to be a cost effective fluid for tight gas zones in the Appalachian Basin, but significantly longer and more effective propped fractures are tough to achieve due to poor proppant transport. There are several factors that affect proppant transportation in a fracture, but one most often overlooked is proppant density. In a paradigm shift from focusing on fluid properties for proppant transport to focusing on proppant characteristics for proppant transport, recent technological advances have been applied as a solution for the Appalachian Basin's cost cutting – production enhancement dilemma. In several detailed case histories from New York, Pennsylvania, Ohio and Northern West Virginia, a novel lightweight proppant has been pumped in an effort to achieve the balance of a more effective fracture within tight economical constraints. The treatment effectiveness of the new lightweight proppant will be analyzed to determine if this new technology truly is a cost effective, production enhancing tool for one of the toughest basins to operate in based on well economics. Stoke's Law calculations indicate that a lightweight proppant with a specific gravity of 1.25 g/cc will have a terminal settling velocity four times less than white Ottawa sand of the same mesh size, 20/40. A simple single phase gas simulator was used to determine initial flow rates and cumulative production for a series of different fracture lengths. It is clear from the simulations that if greater apparent acting fracture lengths can be achieved, flow rates will be increased and reserve-to-production ratios will be decreased.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 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".