MétaCan
Menu
Back to cohort
Record W3117513701 · doi:10.1080/08827508.2020.1861614

Process Optimization and Flowsheet Development for Zinc and Copper Recycling from Reverberatory Furnace Flue Dust

2020· article· en· W3117513701 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

VenueMineral Processing and Extractive Metallurgy Review · 2020
Typearticle
Languageen
FieldEngineering
TopicExtraction and Separation Processes
Canadian institutionsEnvironment and Climate Change Canada
Fundersnot available
KeywordsZincLeaching (pedology)CopperSulfuric acidChemistryFlueFlue gasResponse surface methodologyKeroseneMetallurgyStripping (fiber)Inorganic chemistryWaste managementMaterials scienceEnvironmental scienceChromatography

Abstract

fetched live from OpenAlex

The copper flue dust is an important secondary source for various metals and also a potential threat to the environment. In this study, a process was developed to convert a local copper flue dust containing 20.60% copper, 21% iron and 2.88% zinc into value-added products via a hydrometallurgical route. The response surface methodology was applied for the optimization of base metals leaching by sulfuric acid. Maximum recoveries of 96% for zinc and 76.7% for copper were achieved under the optimum conditions, whereas only 23.92% of the iron content was dissolved. Moreover, various parameters effective on Zn/Fe separation factor were assessed, and favorable separation obtained at pH 3, 2:1 A/O ratio, 20% V/V of D2EHPA in kerosene during 15 minutes. Stripping experiments also showed that 96.35% of zinc was successfully stripped at 1 M sulfuric acid and 2:1 A/O. The mathematical prediction models for leaching, solvent extraction and stripping were proposed and confirmed by statistical analysis and experiments. The proposed process in this study, enhances the copper production in the current leaching plant and makes it possible to recover zinc from industrial waste as a by-product.

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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.778
Threshold uncertainty score0.976

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.001
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.284
Teacher spread0.245 · 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