Metals Removal from Municipal Waste Incinerator Fly Ashes and Reuse of Treated Leachates
Bibliographic record
Abstract
Incinerator fly ash from municipal solid waste is considered as a hazardous waste and can release toxic metals such as Pb and Cd into the environment. This research verifies the performance of a sequential, closed circuit treatment process involving chemical leaching (alkaline washings followed by an acid washings) and precipitation (neutralization at pH=5 and 7). This method also includes the recirculation of treated leachates during the acid washing steps. In total, ten recirculation loops were executed in laboratory pilot scale. The three alkaline leaching steps effectively solubilized the leachable Pb. Two acid leaching steps were required to solubilize Cd, Al, and Zn. Toxic metals, Cd and Pb, were removed from the fly ash at 72 and 30%, respectively. The toxicity characteristic leaching procedure (TCLP), the synthetic precipitation leaching procedure (SPLP), and a simple test using neutral water were conducted on the treated ash in order to validate the process. The results obtained were below the norm for the TCLP and near 0.01mg∕L of Cd and Pb in solution for the other two tests. The removal efficiency during the precipitation step were 21% Cd, 99% Pb, 100% Al, and 63% Zn. The metallic residue produced at pH=7 contained 23% Zn which is potentially recyclable in the metallurgical industry. The recirculation of treated leachates reduced water consumption for the decontamination process by 60%.
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".