Application of a high-intensity cooling system to DC-arc furnace production of ferrocobalt at Chambishi
Bibliographic record
Abstract
A review is presented of the furnace cooling system design and operating developments since the initial furnace start-up in January 2001 of the Chambishi DC-arc furnace to produce ferrocobalt alloy. The furnace operating conditions present a number of challenges to the furnace designers and operators, in particular, to provide a sustainable lining that can withstand the highly corrosive siliceous slag (roughly 50% SiO2). This is exacerbated by the dual requirement of operating this slag in a relatively highly superheated state (?T=400i?½C when tapped at 1550i?½C) to ensure that the ferroalloy can be tapped (estimated 1370i?½C alloy liquidus temperature) prior to atomization. The core design challenge occurs at the alloy-slag interface, where a single refractory type cannot simultaneously meet the dual requirement of both adequate alloy and slag corrosion compatibility. Progression by the fourth furnace campaign to involve a retrofit of the bath sidewall to HATCH high-intensity, water-cooled, copper Waffle coolers and tapblocks is descriptionbed. This involves operation of the entire slag bath, the slag-alloy interface and a portion of the alloy within a more chemically compatible refractory/slag (and possibly at times even an alloy) freeze-lining. Due to the high furnace power density employed (up to 500 kW/m2 hearth area), coupled with the large slag superheat needed, the resulting imposed peak bath sidewall heat fluxes are substantial, especially in the alloy (typically averaging 170 kW/m2), and on occasion have exceeded 1000 kW/m2. The performance of the HATCH Copper Waffle coolers under such aggressive process pyrometallurgical conditions is descriptionbed. Aspects of the design and especially operating strategies to effect sustained production at up to 38 MW power input are also discussed.
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.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".