Calculation Accuracy of Pulsating Flow through the Turbine of SI-Engine Turbochargers - Part 1 Calculations for Choice of Turbines with Different Flow Characteristics
Bibliographic record
Abstract
The paper treats pulsating flow through the turbine of SI-engine turbochargers. In engine design, 1D engine-simulations are very convenient tools for optimization and concept studies. However, they have drawbacks in certain areas. The accuracy, when predicting turbocharger turbine power, is lower than desired. The reason for that is a lack of knowledge about the phenomenon of pulsating flow through the turbine. The background to the problem is described in the paper. This investigation aims at learning more about this unsteady, pulsating flow, on the engine. The method used is to do large parameter changes to several parameters in turbine and manifold designs such as A/R and trim in the turbine and also volume and length of the exhaust manifold. For selection of A/R and trim, as well as an aid in the analysis of measured data, the meanline turbine design software Rital from Concepts NREC [1] was used. Three different turbines were investigated, all with the same mass flow capacity. The three different manifolds were designed to alter the pulsation shape at the turbine inlet. The calculation results show, that through these large parameter changes, it is possible to significantly alter the conditions at both the turbine inlet (shape of pressure and massflow curves) and at the turbine wheel inlet (flow angle and velocity). This has a significant impact on the performance of the turbine and engine.
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.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 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".