MétaCan
Menu
Back to cohort
Record W125704606

Use of Shell Thiopave in asphalt

2010· article· en· W125704606 on OpenAlexaboutno aff
J C Nicholls

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicAsphalt Pavement Performance Evaluation
Canadian institutionsnot available
Fundersnot available
KeywordsAsphaltCompactionDurabilityMaterials scienceShell (structure)Composite materialMixing (physics)StiffnessEnvironmental scienceWaste managementGeotechnical engineeringEngineering
DOInot available

Abstract

fetched live from OpenAlex

Shell Thiopave TM is a patented additive developed by Shell for use in asphalt paving mixtures. The additive is intended to act both as a bitumen extender and as an asphalt mixture modifier. The use of sulphur also has the benefit of lowering the compaction temperature of the asphalt paving mixtures. The additive is added to the pre-heated aggregates and bitumen during the mixing process rather than the sulphur being pre-blended with the bitumen. Experience with the product was obtained with sites in Canada, the USA, Saudi Arabia, Qatar and China. The Marshall properties, deformation resistance, stiffness, fatigue, low temperature crack resistance and water sensitivity are described. Health and safety issues and pavement design implications are considered. The pelletisation of the sulphur by Shell in Thiopave TM has overcome many of the health and safety issues, although strict control of temperature still needs to be maintained. the primary advantages of Thiopave TM-modified asphalt are an increase in strength, stability and possibly durability. The resulting economic advantages are reduced bitumen consumption, reduced pavement thicknesses and lower energy consumption.

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 imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.001
Threshold uncertainty score0.003

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0000.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.0010.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.027
GPT teacher head0.243
Teacher spread0.215 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

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".

Quick stats

Citations0
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicAsphalt Pavement Performance EvaluationFrench-language works237,207