Practical Applications of Bed Scour Calculations: Two Case Studies
Bibliographic record
Abstract
Pipelines can be exposed at water crossings where rivers lower the channel bed. Channel bed scour may cause damage to linear infrastructure such as pipelines by exposing the pipe to the flow of water and sediment. Accurate estimation of depth of scour is therefore critical in limiting damage to infrastructure. Channel bed scour has three main components: (1) general scour, (2) bed degradation, and (3) pool depth. General scour is the temporary lowering of the channel bed during a flood event. Channel bed degradation is the systematic lowering of a channel bed over time. Pool depth is depth of pools below the general bed elevation and includes the relocation of pools that result from river dynamics. Channel degradation is assessed in the field using indicators of channel incision such as channel bed armoring and bank characteristics, through the analysis of long profiles and sediment transport modelling. Pool depth is assessed using long profiles and channel movement over time. The catastrophic nature of bed lowering due to general scour requires a different assessment. A design depth of cover is based on analysis of depth of scour for a given return period (eg. 100-years). There are three main steps to predict general scour: (1) regional flood frequency analysis, (2) estimation of hydraulic variables, and (3) scour depth modelling. Typically, four scour models are employed: Lacey (1930), Blench (1969), Neill (1973), and Zeller (1981), with the average or maximum value used for design depth. We provide herein case studies for potential scour for pipeline water crossings at the Little Smoky River and Joachim Creek, AB. Using the four models above, and an analysis of channel degradation and pool depth, the recommended minimum depth of cover of 0.75 m and 0.142 m, respectively, were prescribed. Variability between scour models is large. The general scour model results varied from 0.45 m and 0.75 m for the Little Smoky River and 0.16 m to 0.51 m for Joachim Creek. While these models are more than 30 years old and do not adequately account for factors such as sediment mobility, they nevertheless do provide usable answers and should form part of the usual toolbox in water crossing scour calculations.
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.003 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.003 | 0.002 |
| Research integrity | 0.003 | 0.001 |
| Insufficient payload (model declined to judge) | 0.008 | 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".