An Investigation Into the Operation of the Twin-Exit Loop-Seal of a Circulating Fluidized Bed Boiler in a Thermal Power Plant and Its Design Implication
Bibliographic record
Abstract
Loop-seal is a critical component of a circulating fluidized bed (CFB) boiler, and yet very little information on its working or design is available in published literature. Among the limited available information, none is on twin-exit loop-seal though it is one of the most commonly used loop-seal in large commercial CFB boilers. To circulate larger amounts of solids, a twin-exit loop-seal provides larger solids flow sections. It receives solids from one standpipe but delivers it through two recycle chambers and two delivery pipes. The present research was conducted in a twin-exit loop-seal of a 3.2 MWth CFB boiler operating in a thermal power plant for cofiring purpose. Data obtained in this industrial unit were supplemented with those collected in a single-exit bench-scale loop-seal in the authors’ laboratory from the single-exit loop-seal in a 65 t/h CFB boiler and a scale model of a 30 MW CFB boiler. The effect of recycle chamber’s aeration on the solids circulation rate was studied for several particle sizes. Results suggest that the total solids circulation rate does not increase proportionately with the increase in loop-seal discharge area provided by the twin-exit loop-seals. The linear horizontal velocities of solids and the minimum aeration in the recycle chambers are comparable to those measured in a single-exit loop-seal. The implication of these new findings on the design procedure of loop-seals is discussed.
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 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 itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, 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".