MétaCan
Menu
Back to cohort
Record W3086733768 · doi:10.3390/pr8091156

On the Application of the FactSage Thermochemical Software and Databases in Materials Science and Pyrometallurgy

2020· article· en· W3086733768 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueProcesses · 2020
Typearticle
Languageen
FieldEngineering
TopicMetallurgical Processes and Thermodynamics
Canadian institutionsPolytechnique Montréal
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsPyrometallurgyThermochemistryRefractory metalsProcess (computing)ElectronicsProcess engineeringComputer scienceMaterials scienceMetallurgyEngineeringChemistry

Abstract

fetched live from OpenAlex

The discovery of new metallic materials is of prime importance for the development of new technologies in many fields such as electronics, aerial and ground transportation as well as construction. These materials require metals which are obtained from various pyrometallurgical processes. Moreover, these materials need to be synthesized under extreme conditions of temperature where liquid solutions are produced and need to be contained. The design and optimization of all these pyrometallurgical processes is a key factor in this development. We present several examples in which computational thermochemistry is used to simulate complex pyrometallurgical processes including the Hall–Heroult process (Al production), the PTVI process (Ni production), and the steel deoxidation from an overall mass balance and energy balance perspective. We also show how computational thermochemistry can assist in the material selection in these extreme operation conditions to select refractory materials in contact with metallic melts. The FactSage thermochemical software and its specialized databases are used to perform these simulations which are proven here to match available data found in the literature.

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.000
metaresearch head score (Gemma)0.001
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.122
Threshold uncertainty score0.169

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
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.017
GPT teacher head0.218
Teacher spread0.201 · 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