MétaCan
Menu
Back to cohort
Record W2038500290 · doi:10.2118/132981-pa

Understanding the Effects of Leakoff Tests on Wellbore Strength

2011· article· en· W2038500290 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 Drilling & Completion · 2011
Typearticle
Languageen
FieldEngineering
TopicDrilling and Well Engineering
Canadian institutionsConocoPhillips (Canada)
Fundersnot available
KeywordsGeomechanicsWellboreGeotechnical engineeringPetroleum engineeringStress (linguistics)Rock mechanicsGeologyDrillingEngineeringMechanical engineering

Abstract

fetched live from OpenAlex

Summary Leakoff tests (LOTs) are performed to test the strength or pressure containment of the shoe after a cement job to help ensure that the new hole has been securely isolated from what has been cased off. A successful LOT can also be used to calibrate the least principal stress (many times, in the case of a vertical well, the minimum horizontal stress), or for geomechanics modeling. This will require initiating a fracture at the wellbore. Because of the near-wellbore stress concentration, for the purpose of geomechanics calibration, it is preferred to take the leakoff to the far-field stress region. To perform this extended LOT (XLOT), a relatively long fracture has to be created. Though an XLOT is needed for these reasons, some engineers tend to refrain from performing this test for fear that the test may damage the wellbore and consequently cause drilling problems. This paper addresses this issue by investigating the effect of wellbore damage on wellbore "strength" or pressure containment. Various issues are discussed to help engineers determine when it may or may not be a concern. This should give practicing engineers the necessary insight into this complex rock-mechanics issue. The discussions are supported with results from analytical and numerical simulations based on rock-mechanics principles.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.510
Threshold uncertainty score0.582

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.053
GPT teacher head0.205
Teacher spread0.152 · 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