MétaCan
Menu
Back to cohort

Estimation of Hydrokinetic Pressure and Fluidic Drag Changes during Pipe Installations via HDD Based on Identifying Slurry-Flow Pattern Change within a Borehole

2017· article· en· W2739169539 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.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Pipeline Systems Engineering and Practice · 2017
Typearticle
Languageen
FieldEngineering
TopicDrilling and Well Engineering
Canadian institutionsUniversity of AlbertaHatch (Canada)
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsBoreholeDragSlurryDrill pipeEngineeringFlow (mathematics)Nominal Pipe SizeDirectional drillingMarine engineeringFluidicsPetroleum engineeringDrillGeotechnical engineeringDrillingMechanical engineeringMechanicsAerospace engineeringMaterials sciencePhysics

Abstract

fetched live from OpenAlex

This paper proposes a new method for hydrokinetic pressure and fluidic drag evaluation of non-Newtonian power-law slurries flowing within a borehole during horizontal directional drilling (HDD) pipe installation operations. The method divides the bore path into three segments, each associated with a different stage of slurry flow pattern. For each stage, assuming the product pipe and drill rod to be placed concentrically within the borehole, a set of coupled equations governing slurry flow within the borehole is derived. Then, to obtain the hydrokinetic pressure and fluidic drag history, the equations are solved at the desired product pipe leading head locations within a given segment. For two actual HDD installations completed in Alberta, Canada, the pullback forces have been collected and are compared against those estimated by the new proposed method and Pipeline Research Council International (PRCI) method. It is demonstrated that the new method can more accurately estimate the pullback forces.

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.001
metaresearch head score (Gemma)0.001
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: none
Teacher disagreement score0.786
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.019
GPT teacher head0.245
Teacher spread0.226 · 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