Leaning on Glass: Industry Pushes for the Use of Glass Fiber-Reinforced Rebar
Bibliographic record
Abstract
This article reviews current knowledge and practice in the use of glass fiber-reinforced polymer (GFRP) rebar in bridge decks to extend deck life by eliminating the typical failure mechanisms associated with conventional or coated steel rebar. GFRP bars have been used as concrete reinforcing for most of the last decade. More than 75 bridge decks have been built with GFRP in the U.S. and Canada alone. All are performing successfully to date. Several key documents now can be used as references for these materials. The American Concrete Institute Committee 440 Document, 440.IR-06 “Guide for the Design and Construction of Concrete Reinforced with FRP Bars,” is one. An important one for the American bridge design community is “AASHTO LRFD Bridge Design Guide Specifications for GFRP Reinforced Concrete Decks and Deck Systems.” GFRP bars’ use is straightforward. What is important is to ensure that they have met key tests under methods outlined by the American Concrete Institute. While the bars have been used in decks, railings, abutments, and approach slabs, the amount of them in each bridge varies widely. The biggest change when using GFRP is that it is linear elastic up to failure and does not yield. Design guidelines suggest very conservative use of them because they are so new. There are also minor differences during concrete pours because they tend to be lighter than conventional steel rebar. However, there is no new training required, and they can be procured with the same procedures.
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.005 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.004 |
| Scholarly communication | 0.003 | 0.006 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.004 | 0.004 |
| Insufficient payload (model declined to judge) | 0.007 | 0.004 |
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".