Low‐temperature experimental model of liquid injection and reaction in a fluidized bed
Bibliographic record
Abstract
In several commercial processes, liquid is injected into a hot fluidized bed, where it undergoes a reaction that generates gases, vapours, and a solid residue. An example is Fluid CokingTM, where large agglomerates resulting from poor liquid‐solid contacting during the liquid injection are undesirable. These agglomerates limit heat and mass transfer, leading to operating problems and a reduction in valuable product yield. Performing experiments in pilot plants for such processes is difficult because of the high required temperature, e.g. 550 °C for Fluid Coking. It is very difficult to determine the proportion of fresh coke residue in agglomerates recovered from a pilot plant, which is essential information for understanding agglomerate formation. This study presents a low‐temperature experimental model that would be much easier and safer to use than a Fluid Coking pilot plant, while providing more information on agglomerate formation and breakup. A solution comprising PlexiglasTM dissolved in acetone and pentane is injected into a fluidized bed of sand particles at 68 °C to simulate heavy oil injection which, in Fluid CokersTM, gives off gases and vapours, simulated by the vapours from the solvents in the Plexiglas solution, and a solid coke residue, simulated by the Plexiglas deposit on sand particles. The experimental model was tested with three separate methods that have been found to reduce agglomerates in commercial or pilot plant Fluid Cokers: increasing the flowrate of atomization steam in liquid spray nozzles, increasing the fluidization velocity, and increasing the bed temperature.
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.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 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".