Improving Shale Production Through Flowback Analysis
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
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
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle