Understanding recovery boiler smelt runoff phenomena
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.
Bibliographic record
Abstract
There is considerable interest in the nature and causes of heavy smelt runoff from recovery boilers because of the role it has played in numerous dissolving tank explosions and for personnel safety around the dissolving tank. Most mills have experienced runoff problems, which can be caused by cleaning plugged spouts, burning down a large bed, low sulfidity smelt, startup with a bed in the unit, and improper firing practices. The peak smelt flow during a runoff is often 3 to 5 times normal and may be much greater in severe cases. Heavy runoffs are self-limiting and typically last less than 30 min. The geometry of the lower furnace plays a significant role in runoff events. Sloped floor units are more vulnerable to smelt pool buildup and heavy runoff when released. Decanting bottom units are inherently more tolerant of smelt pool buildup. Low sulfidity results in smelt with a high melting temperature, making the smelt easy to freeze and difficult to flow. Sulfate-rich slag/deposits falling on the hearth from the upper furnace can contribute significantly to runoff problems by causing dams and spout plugging, increasing the load of smelt pool to be removed, decreasing bed temperatures, and lowering the sulfidity of the smelt leaving the furnace.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| 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 it