Effects of Vibration on Buried Structures from the Removal of Steel Casings during the Installation of Rockfill Columns for Riverbank Stabilization: A Case Study
Bibliographic record
Abstract
Rockfill columns, also known as stone columns, were installed in a riverbank for slope stabilization measures. The goal of this fieldwork was to prevent slope instability of the riverbank while protecting an in-service aqueduct buried in the riverbank. At this site, rockfill columns were installed with the aid of steel casings (sleeves), which were later removed with a vibrodriver. Peak particle velocities were determined at select locations to monitor the ground vibrations during installation of rockfill columns and during extraction of the steel casings. Instrumentation and monitoring were implemented because there was uncertainty about the potential for structural damage to the nearby aqueduct due to ground vibrations during the stabilization works. In this case study, numerical modeling, calibrated versus field measurements in the ground and on the aqueduct, was used to simulate the ground vibrations due to the installation of three rockfill columns close to the aqueduct. Once calibrated, the numerical models were used to evaluate the effects of vibrations in terms of particle velocities in the ground, displacements of the aqueduct, and frequency spectra on the aqueduct walls. The numerical results showed that the highest particle velocities on the aqueduct were from the rockfill columns that had the steel casings located in the same soil layer as the aqueduct. Based solely on the response in terms of particle velocity, damage to the aqueduct is unlikely. However, the numerical results also showed that the aqueduct moves slightly, both vertically and laterally due to the vibration generated while removing the steel casings; and the frequency range of the waves in the ground are within the natural frequency of the soil, which could impose additional movement to the aqueduct if allowed to move freely with the soil. Numerical results and field data also show that even pulling the steel casings without vibration generated propagation of waves in the ground.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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 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".