Avoid Downhole Explosions, Buckled Pipe and Parted Tubing During Snubbing Operations
Bibliographic record
Abstract
Abstract Snubbing involves the running of tubing and related completion equipment into a well while pressure is present at the wellhead. This operation requires the use of specialized equipment that provides control of well pressure and associated fluids at all times, and enables the movement of tubulars and equipment into and out of the well. Petro-Canada chose to create their own snubbing guidelines, and share them with industry, because of situations being encountered that were not adequately described in published recommendations and regulations. The Petro-Canada Snubbing Guidelines are intended to compliment, rather than replace, Industry Recommended Practices on snubbing. Petro-Canada's Snubbing Guidelines contain the following information: Written guidelines, providing information on snubbing and well control equipment, safety requirements, snubbing procedures, and contingent operations.A procedure for preventing downhole explosions when pulling plugs.Pipe buckling calculations, as related to wellbore pressure.Allowable tensile loads, as a function of internal and external pressures.A snubbing operations checklist. This paper addresses i) avoiding downhole explosions, ii) preventing pipe buckling in pipe-light situations, and iii) allowable tensile loads as a function of internal and external pressures.
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.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.011 | 0.003 |
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".