Preserving Pipeline Integrity With Large Diameter Stone Columns at Dead Horse Creek Crossing, Southern Manitoba, Canada
Bibliographic record
Abstract
Pipeline integrity has been threatened at the Dead Horse Creek pipeline crossing in southern Manitoba by a slow-moving slope failure with a potential for crest retrogression. The movement zone extends from the slope crest to the bottom of the creek, a vertical distance of about 25 m and is approximately 80 m long from toe to scarp and 100 m wide along the creek. The slope has degraded over time and is controlled by the combination of local geology, which consists of weak colluvium overlying high plastic clay shale, and creek bank erosion and channel degradation. Saturated soil conditions, a function of poor drainage and elevated seasonal precipitation, have exacerbated the problem over the years. The slope movements have been monitored on a regular basis since 2008 and presented an increasing risk to the integrity of multiple pipelines located in two rights-of-way (ROWs) situated within and immediately adjacent to the failing soil mass. The site is surrounded by various infrastructure and recreational areas that are key to the community, and therefore is considered a high consequence area with respect to potential pipeline failures. To manage the risk and protect pipeline integrity, various stress relief and other mitigating measures have been implemented since 2013 [1], culminating in a major slope rehabilitation project undertaken in 2015, which comprised earthworks, drainage and watercourse improvements, and slope stabilization using stone columns. While the use of stone columns to stabilize embankments is not a new technique, it is not commonly used in the pipeline industry and represents another option for geohazard stabilization in the right situations. This paper presents the slope stabilization techniques employed and discusses the challenges of working on an active moving slope confined by a watercourse and live pipeline assets. The positive benefits of the stabilization measures are illustrated through the use of 2D and 3D numerical modelling, and confirmed through an ongoing geohazard management program that includes site inspection and instrumentation monitoring which continues to show improvements in slope performance post construction.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".