Developing a Performance-Based Joint Sealant Specification for Airport PCC Pavements
Bibliographic record
Abstract
Abstract Despite recent progress to develop a performance-based specification for bituminous sealants applied to asphalt concrete (AC) roadways and runways, a performance-based specification for cold-applied joint sealants for Portland cement concrete (PCC) aprons, taxiways, and parking areas has yet to be mapped and developed. Unique in-service conditions exist on these PCC pavements, where sealants are not only exposed to climatic effects and heavy traffic loads, but also to jet fuel and de-icing fluids. Installation and maintenance conditions are also unique in that it is often necessary to install or replace joint sealants at night or in a very short time so that aircraft traffic disruption is avoided. Hence, special consideration must be provided to ascertain that joint sealants are effective and durable. Recent studies on joint and crack sealants used on airport pavements that experience cold climates indicate that current specifications do not necessarily allow for the selection of durable sealants, and therefore sealant failure can be rapid. To address the issue of premature failure and to extend joint sealant service life, the elements of a performance-based specification for cold-applied joint sealants for PCC airport pavements is reviewed. The benefits of such a specification include the selection of joint sealants for specific local needs, reduced airport pavement maintenance costs, and extended airport PCC pavement service life.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
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 teacher head, 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".