Numerical Investigation of Air-Oil Two-Phase Flow Pattern Transition in the Scavenge Line of an Aeroengine
Bibliographic record
Abstract
Abstract Since most research investments in aeroengines have been targeted at the hot and cold sections, the oil system has remained an area poorly understood. Optimum sizing of the oil system can directly reduce the engine’s weight and specific fuel consumption while maximizing service life. The understanding of air/oil interaction in scavenge lines is required to influence the design of the oil systems and achieve those objectives. The challenge is in the existence of numerous possible flow regimes and phase interactions. In scavenge lines, a complex two-phase flow results from the interaction of sealing airflow and lubrication oil. Scavenge lines can have bends, junctions and sudden area changes which complicates their modeling by amplifying pressure gradients and turbulence generation, and causing the flow to change morphology (annular, slug, stratified, bubbly, mist, etc.). Several multiphase flow approaches have been developed to model two-phase flow in straight scavenge lines. However, up until now, no methodology is preferred by the community for simulating two-phase flow in such application. There are still many unknowns regarding the modeling of turbulence, phase interaction and the compressibility of immiscible mixtures such as air and oil. The present study compares the performance of two numerical models: Volume of Fluid (VOF) and Algebraic Interfacial Area Density (AIAD), for simulating the air/oil flow in a suddenly expanding scavenge line against the experimental data of Ahmed et al. [1–2]. The AIAD model is a two-fluid Eulerian approach newly implemented on Ansys Fluent. Discrepancies between the two models for predicting pressure loss and void fraction are evaluated and discussed into details. The flow regime before and after the sudden expansion is identified using iso-surfaces of the void-fraction and compared against visual data. Based on the results presented, recommendations are formulated for further work regarding the calibration of AIAD modeling parameters.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".