MétaCan
Menu
Back to cohort
Record W4413227027 · doi:10.1002/suco.70275

Numerical modeling of rolling loading of bridge deck with different reinforcement types

2025· article· en· W4413227027 on OpenAlex
Chongxi Gao, Akram Jawdhari, Amir Fam

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueStructural Concrete · 2025
Typearticle
Languageen
FieldEngineering
TopicStructural Behavior of Reinforced Concrete
Canadian institutionsPerformance Plants (Canada)Queen's University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsRebarStructural engineeringDeckFinite element methodStiffnessNonlinear systemFibre-reinforced plasticBridge (graph theory)SlabReinforcementEngineering

Abstract

fetched live from OpenAlex

Abstract This paper presents a complex nonlinear finite element model of a full‐scale bridge deck that was experimentally studied under both pulsating and rolling load. The bridge deck was designed to incorporate three different reinforcement designs implemented at various portions of the slab to maximize test efficiency. The different stiffness across the longitudinal span poses a challenge for the finite element model to simulate the behavior of the bridge deck. The deck is comprised of zones incorporating different types of reinforcements, namely conventional steel rebar, glass fiber‐reinforced polymer (GFRP) rebar, and a new GFRP stay‐in‐place structural form system. All zones are integrated in one monolithic cast. The finite element model features characteristics such as nonlinear material laws, failure criteria, and interfacial relations for parts in contact. To verify the applicability and adequacy of selected material models, 14 specimens representing three different concrete structures and test setups from independent studies were modeled and validated. A model of the bridge deck was then created and validated using the data from the experiment featuring service load level.

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: Empirical
Teacher disagreement score0.050
Threshold uncertainty score0.975

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.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.012
GPT teacher head0.239
Teacher spread0.227 · 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