MétaCan
Menu
Back to cohort
Record W2133547547 · doi:10.1016/s1001-0521(06)60087-9

Thermodynamic database development—modeling and phase diagram calculations in oxide systems

2006· article· en· W2133547547 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

VenueRare Metals · 2006
Typearticle
Languageen
FieldEngineering
TopicMetallurgical Processes and Thermodynamics
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsExtrapolationPhase diagramCALPHADSpinelDatabaseOxideMaterials sciencePhase (matter)Computer scienceProcess engineeringThermodynamicsMetallurgyChemistryMathematicsPhysics

Abstract

fetched live from OpenAlex

The databases of the FactSage thermodynamic computer system have been under development for 30 years. These databases contain critically evaluated and optimized data for thousands of compounds and hundreds of multicomponent solutions of solid and liquid metals, oxides, salts, sulfides, etc. The databases are automatically accessed by user-friendly software that calculates complex multiphase equilibria in large multicomponent systems for a wide variety of possible input/output constraints. The databases for solutions have been developed by critical evaluation/optimization of all available phase equilibrium and thermodynamic data. The databases contain parameters of models specifically developed for different types of solutions involving sublattices, ordering, etc. Through the optimization process, model parameters are found which reproduce all thermodynamic and phase equilibrium data within experimental error limits and permit extrapolation into regions of temperature and composition where data are unavailable. The present article focuses on the databases for solid and liquid oxide phases involving 25 elements. A short review of the available databases is presented along with the models used for the molten slag and the solid solutions such as spinel, pyroxene, olivine, monoxide, corundum, etc. The critical evaluation/optimization procedure is outlined using examples from the Al2O3-SiO2-CaO-FeO-Fe2O3 system. Sample calculations are presented in which the oxide databases are used in conjunction with the FactSage databases for metallic and other phases. In particular, the use of the FactSage module for the calculation of multicomponent phase diagrams is illustrated.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.313
Threshold uncertainty score0.617

Codex and Gemma teacher scores by category

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.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.016
GPT teacher head0.241
Teacher spread0.225 · 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