MétaCan
Menu
Back to cohort
Record W3187984769 · doi:10.1139/cgj-2021-0093

Optimization of grouting method and axial performance of pressure-grouted helical piles

2021· article· en· W3187984769 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCanadian Geotechnical Journal · 2021
Typearticle
Languageen
FieldEngineering
TopicGeotechnical Engineering and Soil Stabilization
Canadian institutionsWestern University
Fundersnot available
KeywordsGroutPileNozzleGeotechnical engineeringStructural engineeringMaterials scienceEngineeringMechanical engineering

Abstract

fetched live from OpenAlex

Pressure-grouted helical pile (PGHP) is an innovative piling system that allows a significant increase in helical pile capacity with relatively low additional cost. The pile is constructed by applying pressurized grout during the installation of conventional helical piles. The grout is injected into the ground through two nozzles welded to the hollow pile shaft. This paper presents a comprehensive laboratory study to investigate the effect of three different nozzle configurations on the shape and axial performance of PGHP. The results reveal a significant increase in the PGHP shaft resistance over that of the un-grouted helical pile due to the formation of a continuous grout column with a larger diameter, higher friction angle at the pile–soil interface, and higher lateral earth pressure around the pile. The shape and diameter of the grout column created depend on the nozzle configuration used for grout injection. An increase in the end-bearing resistance is observed due to grout dissipation into the supporting soil voids. The study also shows that PGHPs installed with the third nozzle configuration have the fastest installation rate and the highest compression and pullout resistances. Thus, the third nozzle configuration is recommended for PGHP 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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.856
Threshold uncertainty score0.466

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.007
GPT teacher head0.202
Teacher spread0.195 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it