MétaCan
Menu
Back to cohort
Record W2024052550 · doi:10.1680/macr.2004.56.2.99

Development of volcanic pumice based cement and lightweight concrete

2004· article· en· W2024052550 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

VenueMagazine of Concrete Research · 2004
Typearticle
Languageen
FieldEngineering
TopicInnovations in Concrete and Construction Materials
Canadian institutionsToronto Metropolitan University
FundersPapua New Guinea University of Technology
KeywordsPumicePortland cementCementShrinkageAggregate (composite)Volcanic ashVolcanoMaterials scienceCompressive strengthFly ashGeotechnical engineeringComposite materialGeologyGeochemistry

Abstract

fetched live from OpenAlex

The results of investigations on the suitability of using volcanic pumice (VP) as cement replacement material and as coarse aggregate in lightweight concrete production are reported. Tests were conducted on cement by replacing 0–50% of cement by mass and on concrete by replacing 0–100% of coarse aggregate by volume. The physical and chemical properties of VP were critically reviewed to evaluate the possible influence on both fresh and hardened properties of cement and concrete. The standard tests on different mixtures of Portland cement and volcanic pumice powder (VPP) mixtures provided encouraging results, comparable to those for blended Portland fly ash cement, and showed good potential for manufacturing Portland volcanic pumice cement with higher setting time and low heat of hydration using up to 15% of VPP. The properties of volcanic pumice concrete (VPC) using different percentages of volcanic pumice aggregate were evaluated by conducting a comprehensive series of tests on workability, strength, shrinkage and permeability. It is concluded that VPC has sufficient strength and adequate density to be accepted as structural lightweight concrete. Design charts are presented to evaluate mix design parameters of VPC.

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.001
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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.035
Threshold uncertainty score0.638

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.038
GPT teacher head0.296
Teacher spread0.257 · 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