The Use of Hydrogen as a Potential Reductant in the Chromite Smelting Industry
Bibliographic record
Abstract
The chromium (Cr) content of stainless steel originates from recycled scrap and/or ferrochrome (FeCr), which is mainly produced by the carbothermic reduction of chromite ore. Ever-increasing pressure on FeCr producers to curtail carbon emissions justifies migration from traditional FeCr production routes. The interaction between hydrogen and chromite only yields water, foregoing the generation of significant volumes of CO-rich off-gas during traditional smelting procedures. For this reason, the use of hydrogen as a chromite reductant is proposed. In addition to thermodynamic modelling, the influence of temperature, time, and particle size on the reduction of chromite by hydrogen was investigated. It was determined that, at the explored reduction parameters, the iron (Fe)-oxides presented in chromite could be metalized and subsequently removed by hot-acid leaching. The Cr-oxide constituency of chromite did not undergo appreciable metalization. However, the removal of Fe from the chromite spinel allowed the formation of eskolaite with the composition of (Cr1.4Al0.6)O3 in the form of an exsolved phase, which may adversely affect the reducibility of chromite. The study includes the limitations of incorporating hydrogen as a reductant into existing FeCr production infrastructure and proposes possible approaches and considerations.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
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".