MétaCan
Menu
Back to cohort
Record W4387663114 · doi:10.1080/15732479.2023.2266745

Numerical study of precast segment columns with shear keys under vehicle collision

2023· article· en· W4387663114 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.

Bibliographic record

VenueStructure and Infrastructure Engineering · 2023
Typearticle
Languageen
FieldEngineering
TopicStructural Response to Dynamic Loads
Canadian institutionsMinistry of Education and Child Care
Fundersnot available
KeywordsPrecast concreteStructural engineeringShear (geology)EngineeringCollisionGeotechnical engineeringComputer scienceMaterials scienceComposite material

Abstract

fetched live from OpenAlex

It is commonly understood that precast technology has been rapid development and application due to its short construction period and environmental friendly, etc. Among all precast structure, precast segment column has been widely concerned in the substructure of bridges. The precast segment columns will not only suffer from the earthquake loads but also be subjected to the collision of vehicle and barges. The concrete segments of precast segment column subjected to vehicle collision are prone to slip and even punching failure. In order to enhance the shear resistance between concrete segments, the precast segment column with shear key is designed, and the dynamic performance and shear mechanism under vehicle collision are analysed in this work. The results indicate that the shear key improves the shear capacity between segments and effectively reduces the relative displacement between segments, and makes the deformation mode of precast segment column change from shear type to bending type under vehicle collision. The maximum impact force of precast segment column with shear key is larger than that without shear key. Besides, the shear mechanism of precast segment column is revealed, and the calculation formula of local shear resistance is proposed.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.590
Threshold uncertainty score1.000

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.001
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.004
GPT teacher head0.195
Teacher spread0.191 · 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