Assessing Friction Coefficient in HDD Using Analytical Models
Bibliographic record
Abstract
In horizontal directional drilling (HDD), accurate determination of the pullback force for pipe installation (pullback) during the design phase is critical to the success of the project. For the calculation of pullback force, a friction coefficient of 0.3 is generally suggested for the lubricated borehole in the design. In this paper, friction coefficients are determined from data collected during running in hole (RIH), i.e., moving the drill assembly toward the cutting face without drilling, for the drilling of the pilot hole and reaming stage. This gives a friction coefficient that is calculated for hole conditions similar to those in the pullback process. The friction coefficient is back-calculated based on the equilibrium of thrust force (μF) and torque (μT), using three models. The main difference among the three models is whether or not the model incorporates the effect of annular pressure at the drill bit and viscosity of drilling fluid in the calculation. Results indicate the friction coefficient obtained based on the equilibrium of thrust force is larger than that for equilibrium of torque. The range of μF is between 0.10 and 0.40 and that of μT is between 0.05 and 0.2. This paper also compares three different models based on the calculated friction coefficients to identify the effect of annular pressure and viscosity on the calculation. The results indicate that the difference in terms of the calculated friction coefficient between the models is less than 10%. This paper provides an overall idea of the range of the friction coefficient for a clean hole in HDD based on data collected during an HDD project.
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
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".