Seton Storm Trunk: Conventional and Trenchless Installation
Bibliographic record
Abstract
The Seton Storm Trunk and Outfall to the Bow River were designed to convey clean stormwater flows from the Rangeview and Ricardo Ranch neighborhoods being developed in southeast Calgary, Alberta, Canada. The Seton Storm Trunk has a total length of 2.3 km with pipe diameters ranging from 900 to 1,500 mm and provides storm outlet servicing for a total area of 614 ha. Approximately 2.0 km of the storm trunk was installed using conventional open-cut installation. The main challenge was when the storm trunk reaches the top edge of the Bow River escarpment where the ground elevation drops more than 50 m in a horizontal distance of approximately 175 m. Several groundwater springs along the toe of the escarpment where it meets the Bow River floodplain make the installation even more challenging. There are also several known areas where soil creep is occurring to the east of the storm trunk alignment, likely due to the shallow groundwater table in combination with surface water drainage paths. A review of available options and a triple bottom line analysis, where economic, social, and environmental issues are evaluated equally, determined that Horizontal Directional Drilling (HDD) was the most viable and cost-effective option that would have the least environmental and social impacts on the escarpment slope. To meet the hydraulic requirements of the project, it was determined that a 900 mm HDPE pipe installed at a slope of just over 14% was required for capacity. At this slope, an energy dissipation structure was required at the bottom prior to the flow being discharged through the outfall to the Bow River. The energy dissipation uses an innovative design that uses hydraulic jumps to dissipate the energy at the bottom of the escarpment. The drill entry was located approximately 135 m back from the top of the escarpment, 60 m north of where the gravity storm trunk connects to the HDD section through a specially designed hydraulic drop structure. The structure and piping include air management features to avoid air entrapment in the pipe, thus compromising the hydraulic capacity of the system. This paper presents an overview of the challenges, both geotechnical and hydraulic, that the design team had to overcome, which resulted in the very complex HDD plan necessary to complete the work.
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.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.011 | 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".