Analysis of Technological Issues, Related to Processing of Alunite at Ganja Alumina Plant (GAP), and Ways of Their Solving
Bibliographic record
Abstract
In 1965, the Ganja Alumina plant (GAP) started implementing an alkaline reduction technology for processing of alunite ore on an industrial scale. Technological deficiencies, together with design errors, led to unprofitable production. Since the plant was established, studies have been conducted to eliminate deficiencies in the reduction process, through alkaline technology and hardware design. A “reversed” scheme was developed for hydrochemical processing of alunite restored with the conversion of sodium sulphates using a KOH solution. Despite the elimination of several shortcomings in alkaline reduction technology, certain drawbacks remained, in particular: 1) significant emission of gas and dust from the kilns of fluidized bed furnace during roasting and recovery; 2) insufficient time for recovery of alunite powder, which complicates and worsens the technological and economic aspects of the process; 3) passivation of alumina in the roasting and reduction processes; 4) low yield alumina yield in the commercial product (≤ 75%); and 5) a significant amount of solid waste: 5 tonnes of red sludge per 1 tonne of AL2O3, and errors. As a result, the alunite ore processing line ceased production in 1992 and has not operated since. This article is devoted to the development of new technologies and the improvement of a new potash-alkaline method and new soda-alkaline technology for processing alunite ores. The replacement of potash with soda (sodium carbonate), using new soda-alkaline technology, is proposed. Processing of solution from the first leach with sodium sulphate by conversion with KCl leads to production of K2SO4 and NaCl. Use of the soda-alkaline technology allowed us to obtain the same products as with potash-alkaline technology, with an additional product – table salt. The fluidized bed furnace was replaced by a new type of kiln.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".