Impact of Injection Rate on Flow Mixing during the Refining Stage in an Electric Arc Furnace
Bibliographic record
Abstract
During the refining stage of electric arc furnace (EAF) operation, molten steel is stirred to facilitate gas/steel/slag reactions and the removal of impurities, which determines the quality of the steel. The stirring process can be driven by the injection of oxygen, which is carried out by burners operating in lance mode. In this study, a computational fluid dynamics (CFD) platform is used to simulate the liquid steel flow dynamics in an industrial-scale scrap-based EAF. The CFD platform simulates the three-dimensional, transient, non-reacting flow of the liquid steel bath stirred by oxygen injection to analyze the mixing process. In particular, the CFD study simulates liquid steel flow in an industrial-scale EAF with three asymmetric coherent jets, which impacts the liquid steel mixing under different injection conditions. The liquid steel mixing is quantified by defining two variables: the mixing time and the standard deviation of the flow velocity. The results indicate that the mixing rate of the bath is determined by flow dynamics near the injection cavities and that the formation of very low-velocity regions or ‘dead zones’ at the center of the furnace and the balcony regions prevents flow mixing. This study includes a baseline case, where oxygen is injected at 1000 SCFM in all the burners. Two sets of cases are also included: The first set considers cases where oxygen is injected at a reduced and at an increased uniform flow rate, 750 and 1250 SCFM, respectively. The second set considers cases with non-uniform injection rates in each burner, which keep the same total flow rate of the baseline case, 3000 SCFM. Comparison between the two sets of simulations against the baseline case shows that by increasing the uniform flow rate from 1000 to 1250 SCFM, the mixing time is reduced by 10.9%. Moreover, all the non-uniform injection cases reduce the mixing time obtained in the baseline case. However, the reduction in mixing times in these cases is accompanied by an increase in the standard deviations of the flow field. Among the non-uniform injection cases, the largest reduction in mixing time compared to the baseline case is 10.2%, which is obtained when the largest flow rates are assigned to coherent jets located opposite each other across 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.
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.001 |
| 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".