A Two-Stage Process Using Recycled Acidic And Basic Sludges For Treating Acidic Rock Drainage
Bibliographic record
Abstract
A two-stage (I and II) treatment has been studied at lab-scale using recycled acidic and basic sludge to treat acidic rock drainage (ARD) containing high levels of heavy metals. In stage I, ARD is partially neutralized to pH 4–5 with a mixture of lime and recycled basic sludge to generate acidic sludge. The acidic sludge is then separated for disposal as nonhazardous wastes as classified by TCLP testing. In stage II, the pH of water is further raised to 9–10 with lime neutralization, in the presence of lignosulfonates. Aeration, followed by adding small amounts of recycled acidic sludge, or its mixture with ferrous solution, or injection of ferric solution decreases the pH of water to 8.5–9.5. Thus, metals are removed from water as a basic sludge, which consists mainly of metal hydroxides. The basic sludge is separated from the effluent in stage II and entirely recycled to stage I, where its unstable metal components are leached into the water. It now changes into acidic sludge that is composed of metal complexes with a low TCLP leachability at pH 5. This recycling allows the neutralization potential of basic sludge to be completely utilized. The separation of acidic sludge from the system not only can minimize lime scale formation but also avoid consuming additional lime to increase wastes. The application of lignosulfonates provides lubrication, which promotes the smooth flow of both liquid and solid wastes. This two-stage process can produce a high quality effluent in addition to saving >32% of total chemical costs, and reducing >20% of sludge amounts in comparison with the conventional lime neutralization process.
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.001 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".