MétaCan
Menu
Back to cohort
Record W4402059423 · doi:10.1061/9780784485590.020

Raise Bore Case Study: Application of Raise Bore Installation for Pipeline Construction on Steep Slopes

2024· article· en· W4402059423 on OpenAlex
Arend Deelen, Colby A. Smith, Riley Bartel

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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldMaterials Science
TopicEngineering and Material Science Research
Canadian institutionsnot available
Fundersnot available
KeywordsPipeline (software)GeologyPetroleum engineeringWellboreMining engineeringComputer scienceEngineeringMechanical engineering

Abstract

fetched live from OpenAlex

The construction of the Coastal GasLink (“CGL”) Pipeline encountered a multitude of steep slopes, primarily in the high-altitude sections within the Coastal Mountains near Kitimat, BC. Steep slope pipeline construction offers unique design, safety, and constructability challenges. Varying installation methodologies were utilized by CGL, including the application of a mining technique referred to as a Raise Bore. A Raise Bore is a trenchless installation method consisting of a near-vertical bored section and a horizontal blasted drift tunnel where the pipeline can be installed. This technology has been used extensively in the mining industry and TC Energy utilized this method to install a section of pipe on a previous project in Mexico. The use of a Raise Bore on CGL was the first of its kind for pipeline construction in Canada. This paper discusses the benefits and challenges associated with the implementation of a Raise Bore, as well as the design inputs, execution, risk analysis, and lessons learned from the CGL 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.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.114
Threshold uncertainty score0.327

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.023
GPT teacher head0.328
Teacher spread0.305 · 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