MétaCan
Menu
Back to cohort
Record W1970480393 · doi:10.1520/jte100260

Development of a Viscosity Specification for Hot-Poured Bituminous Sealants

2007· article· en· W1970480393 on OpenAlex

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.

Bibliographic record

VenueJournal of Testing and Evaluation · 2007
Typearticle
Languageen
FieldEngineering
TopicAsphalt Pavement Performance Evaluation
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsSealantViscometerViscosityMaterials scienceAsphaltComposite materialRepeatabilityForensic engineeringEngineering

Abstract

fetched live from OpenAlex

Abstract Current crack sealant specifications focus on using simple empirical tests such as penetration, resilience, flow, and bonding to cement concrete briquettes (ASTM D 6690) [1] to measure the ability of the material to resist cohesive and adhesive failures. There is, however, no indication of the pertinence of these standard tests to predict the success of field installation and sealant performance. In an effort to bridge the gap between sealant fundamental properties and field performance, performance-based guidelines for the selection of hot-poured crack sealants are currently being developed. This paper proposes a new viscosity test procedure to help assess the propensity of sealants to wet the crack surface during installation. The proposed procedure calls for the use of a Brookfield rotational viscometer equipped with a modified spindle rod and an SC4-27 spindle at a speed of 60 r/min. Sealants are heated 20 min at the recommended installation temperature and the viscosity is measured after 30 s of spindle rotation in the hot sealant. These experimental conditions provide viscosities representative of sealant viscosity at shear rates during field application. The repeatability for within laboratory and between laboratories was found to be 5.4 and 17 %, respectively. This repeatability is comparable with the corresponding variability of the SuperPave viscosity test for asphalt binders.

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.005
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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.688
Threshold uncertainty score0.255

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.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.111
GPT teacher head0.332
Teacher spread0.221 · 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