MétaCan
Menu
Back to cohort
Record W2901420783 · doi:10.2118/193353-ms

Flow Control Devices in SAGD - A System-Based Technology Solution

2018· article· en· W2901420783 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSPE Thermal Well Integrity and Design Symposium · 2018
Typearticle
Languageen
FieldEngineering
TopicOil and Gas Production Techniques
Canadian institutionsDevon Energy (Canada)
Fundersnot available
KeywordsWorkflowSoftware deploymentComputer scienceProduction (economics)Control (management)Steam injectionPetroleum engineeringProcess engineeringEngineeringSystems engineeringRisk analysis (engineering)Business

Abstract

fetched live from OpenAlex

Abstract Flow Control Devices (FCDs) in SAGD applications have succeeded and failed to varying degrees and their use has not been overly pervasive or fully accepted yet. However, recently it has been publicized that FCD technology has achieved upwards of 100% improvement in SAGD oil production and potential improvements in steam oil ratios (SOR), which has continued to spark interest in its application. SAGD reservoirs are inherently heterogeneous and this presents distinct operational complexities when attempting to expedite the production of the oil while attempting to avoid steam breakthrough. Producing the steam reduces the thermal efficiency of the project which results in an increased SOR while also creating a high potential of compromising the mechanical integrity of the production liner. FCDs can mitigate the operational negatives and enhance the operational positives, however, they are not a ‘silver bullet’ for all ailments and their implementation needs to be carefully planned. This paper reviews FCD implementation workflows and highlights recent downhole instrumentation technology advancements that enhance FCD performance analysis and supports better deployment designs that should improve the economic viability of existing and upcoming SAGD projects.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.748
Threshold uncertainty score0.635

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.011
GPT teacher head0.213
Teacher spread0.202 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it