Effect of Bridge Deck DesignMethodology on Crack Control
Bibliographic record
Abstract
At present, the Idaho Transportation Department (ITD) Bridge Design Manual allows engineers to use the American Association of State Highway and Transportation Officials (AASHTO) empirical method to design concrete bridge decks. However, the ITD Bridge Section would like to compare their design practices to those employed by other state departments of transportation. The Bridge Section is also interested in the ability of the empirical deck design method to control deck cracking. AASHTO’s empirical deck design method and traditional design method are summarized. The authors reviewed the literature regarding the effect of bridge deck design methodology on deck cracking. Many researchers agree that the empirical bridge deck design method needs to be modified to limit cracking. For example, Frosch and Radabaugh believe that the empirical method does not require a large enough reinforcement ratio to adequately control cracking. Others such as Krauss believe that the deck‐to‐girder stiffness has a greater effect on deck cracking and should be increased in the empirical method. We also surveyed bridge deck design methods and typical deck designs for all of the states in the United States. Bridge deck properties such as deck thickness, rebar size and rebar spacing from other states were compared to those specified by ITD. Most states and Canada use a significantly smaller spacing and larger reinforcement bar size. The authors believe that reducing the spacing and increasing the size of rebar would mitigate ITD’s deck cracking problem, although the degree to which deck crack spacing and width would be mitigated would require further research.
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.010 | 0.033 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".