Response to the Paper Entitled "Transition to Superpave Performance Grades in Western Canada" Presented to the Canadian Technical Asphalt Association's Annual Conference in 2012
Bibliographic record
Abstract
In order to ensure that western Canadian road agencies receive the same quality asphalt they have in the past with penetration/viscosity specifications, the adoption of Performance Graded Asphalt Cement (PGAC) specifications require some adjustments. In this response, the Author provides a summary of Husky Energy's position in regards to the adoption of PGAC specifications in western Canada. The asphalt properties from the different crudes have been evaluated. Relying on our expertise with asphalt evaluations from different crudes, we selected a number of asphalts based on the quality according to the PG, the temperature range between the high- and low-temperature PG, and the A grade designations using current western Canadian penetration/viscosity specifications. These asphalts were also selected due to their resemblance to the properties of asphalts produced from Lloyd Blend and Cold Lake crudes, which are used for the majority of asphalt cement production in western Canada. From these evaluations, the adoption of specific PG specifications in western Canada are recommended. These specifications will increase the assurance that road agencies will receive the same quality of asphalts they have under the western Canadian penetration/viscosity specifications. (A) For the paper referred to in this report see ITRD record number 201306RT351E. For the covering abstract of this conference see ITRD record number 201402RT334E.
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.002 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.006 | 0.001 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.009 | 0.006 |
| Insufficient payload (model declined to judge) | 0.049 | 0.014 |
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".