Bibliographic record
Abstract
Once a horizontal well is hydraulically fractured, the next step is to clean up the well by flowing it back to remove water and loosen proppant from the wellbore. Most shale producers in North America have given little thought to this flowback stage and see it merely as a prelude to the cash-flow generating production stage. However, a few companies have come to realize it represents a valuable opportunity to learn more about their wells in a week or two than their competitors are learning after several months of production. Essentially, flowback data is a bridge between what happened during a completion and what will happen as hydrocarbons are produced. An important driver shared by all the interested producers is that for the most part, they are already required to record the flowback stage per US and Canadian regulations. “So arguably, the cost of collecting this data is nil,” said James Crafton, president of consultancy firm Performance Sciences, who has been working with service companies and shale producers on different flowback issues for more than 15 years. Crafton and others involved in this area have long been trying to convince the shale business that how a well is flowed back is often as important as the completion itself and that by ignoring this maxim, they are leaving money on the table. “It is that simple,” he said. “The frustration for me is that the data is there. We have the data, but nobody has the time or perceives the value to interpret the data.” But there are a few outliers crunching the numbers. Companies including Devon Energy are using the early production and flowing pressure data of flowback fluids to establish their production benchmarks. Nexen Energy is among those also using flowback data to quickly screen the effective size of fracture designs, determine key reservoir properties, and to predict long-term production. Ongoing flowback research is looking at the chemical makeup of flowback fluids to see what else can be learned about shale reservoir behavior. Salty Flowback Research May Explain Fluid Movement in Shale Letting It Soak In: Delaying Flowback Delivers Unique Results Following Flowback With Chemical Tracers
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.004 | 0.007 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.005 | 0.006 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.014 | 0.005 |
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".