Analysis of Torsional Stick-Slip Situations from Recorded Downhole Rotational Speed Measurements
Bibliographic record
Abstract
Summary The use of recorded downhole rotational speed measurements with a bandwidth up to 9 Hz gives new insights into the conditions under which stick-slip torsional oscillations occur. Observations made while drilling two reservoir sections have shown that, out of all the stick-slip situations identified, 72% of them for one well and 64% for the other well occurred in off-bottom conditions. In these off-bottom conditions, stick-slip was systematically observed while starting the topdrive (TD) until a sufficiently high TD rotational velocity was requested. For these two sections, off-bottom stick-slip was either related to using TD speeds below 120 rev/min or to reaming down during reciprocation procedures. In on-bottom conditions, stick-slip events occurred predominantly when the TD speed was less than 120 rev/min (53 and 32% of the on-bottom cases) but also in association with downlinking to the rotary steerable system (RSS) (23 and 46% of the on-bottom cases), and this, even though the TD speed was larger than 120 rev/min. These on-bottom stick-slip situations did not necessarily occur at a very high weight on bit (WOB) because 98% of them for one well and 46% for the other well took place when the WOB was lower than 10 ton. Downhole measurements have shown that when the drillstring is subject to strong stick-slip conditions, the downhole rotational speed changes from stationary to more than 300 rev/min in just a fraction of a second. Direct observations of downhole rotational speed at high frequency help in discovering conditions that were not suspected to lead to large torsional oscillations. This new information can be used to improve drilling operational procedures and models of the drilling process, therefore enabling increased drilling efficiency.
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.000 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
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".