Simplified Equations for Moment and Shear in Bridge GirdersResulting from AASHTO Truck Loading
Bibliographic record
Abstract
In bridge analysis, bridge designers require the maximum loads applied on bridge traffic lanes in order to determine the appropriate structural design including materials, girder spacing, and cross-section sizes for the bidding procedure.In order to achieve that, designers have to go through an iterative trial and error process which takes a considerable amount of time and may result in overestimation at the bidding stage.In the case of bridge design, there are no such tables which hinders the preliminary assessment of project value and bid cost.As such, this paper outlines a research conducted to develop traffic load equations and tables based on the 2020 AASHTO LRFD Bridge Design Specifications.By utilizing this method, engineers will save time in the design process, and reduce project bid cost by minimizing overdesigned and overestimated structural section sizes for project tender documents.In this research, moving load equations and tables were created based on single-lane bridge models for single span and two-span bridge configurations in SAP2000 software.Truck load arrangements, based on AASHTO LRFD design specifications, were applied and results obtained using moving load approach.Finally, the data generated from the parametric study was used to develop empirical expressions for design moment (MT) and shear (VT) for the use by bridge designers.
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.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.008 | 0.003 |
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".