Remedial Protection of a Pipeline Crossing of the River Wye, UK
Bibliographic record
Abstract
This project is of interest to those involved in construction, siting and repair of pipeline crossings of rivers, streams and estuaries. In early 1999, Mainline Pipelines Limited discovered that their pipeline crossing of the River Wye had been exposed by river scour. Originally laid in 1972, the line provides petroleum products main supply from the port at Milford Haven to the Midlands, England, and operates at a high pressure. A break in or temporary shutdown of the pipeline would have had serious implications. Remedial protection options were needed rapidly, to ensure the integrity of the pipeline. A review of historical air photographs and maps, dating back to 1888, showed that the meandering channel of the River Wye has shifted to the north at an average rate of 0.65m per year. Thus, the remedial works would have to account for ongoing vertical and lateral scour. It was recognized that river training works would be required at the site to ensure continued protection of the pipeline in the long-term. The recommended design and remedial construction techniques allowed for safety issues, the potential impact on the river ecology, recreational river users, the river hydrology and restricted access to the steep northern riverbank. The design comprised filling of the eroded riverbed and bank with rock aggregate and placing a protective layer of graded rock riprap. Grout filled fabric formwork bags were placed beneath the pipeline to minimise deflection and the development of unacceptable stresses in the exposed length during rock placement. Rock filled wire mattresses were placed immediately on top of the pipeline to protect it from point loading of the angular riprap. A satellite guided positioning system was used to control material placement, and environmental monitoring of river water quality was carried out continuously during 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 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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.004 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.018 | 0.002 |
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".