Preserving Critical Stormwater Storage Assets at Pipeline Terminal
Bibliographic record
Abstract
Abstract A slope failure compromised the integrity of a critical stormwater storage facility at a petroleum storage terminal within northern Alberta. Through periodic ground inspections and a review of LiDAR and aerial imagery, significant lateral deformation of a lined stormwater pond was identified. The potential for pond overflow and uncontrolled stormwater release into the natural environment due to compromised discharge outlets and liner integrity posed an operational and environmental risk. A fast-tracked review and assessment of both the historical and as-built construction details, a good understanding of the regional geology, and geotechnical investigation and instrumentation were required to identify remedial measures that could be implemented to restore the pond prior to the onset of major storm events. Geotechnical investigation and assessment showed weak zones in the bedrock at shallower depths than were historically encountered at the site. Spatial constraints, uncontrolled fill placement in close proximity to the pond, expansion of the pond following original construction, and compromised subsurface drainage were identified as factors that may have contributed to the failure. Assessment of remedial options considered impacts relative to both local and global factors of safety. The selected remedial option was a combination of slope unloading, shear key construction, and improved drainage with the design and construction occurring within a timeframe of 3 months to minimize the time that the pond was out of service. The paper highlights the challenges associated with the slope unloading and shear key construction that were required to control the ground movements. An approach involving sequential excavation and replacement was adopted to manage the risks associated with shear key construction. In addition, directional drill methods were incorporated to install some of the drainage measures due to the risk associated with an open cut approach. The project was fast-tracked to minimize exposure to high precipitation and limited stormwater storage capacity.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.003 | 0.001 |
| 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.005 | 0.001 |
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".