Influence of exit-to-throat width ratio on performance of high pressure convergent-divergent rotor in a vaneless counter-rotating turbine
Bibliographic record
Abstract
This paper describes the redesign of a high pressure rotor (with exit Mach number around 1.5) for the vaneless counter-rotating turbine by choosing adequate exit-to-throat width ratio. Based on the previous design analysis and test results, effects of the exit-to-throat width ratio on the performance of the transonic turbine cascade were proposed. In order to investigate the influence of the exit-to-throat width ratio on the performance of the turbine cascade, a flow model of the convergent-divergent turbine cascade was constructed by using the theory of Laval nozzle. Then a method on how to choose the adequate exit-to-throat width ratio for the turbine cascade was proposed. To validate the method, it was used to calculate the adequate exit-to-throat width ratio for the high pressure rotor of the vaneless counter-rotating turbine. The high pressure turbine rotor was redesigned with the new exit-to-throat width ratio. Numerical simulation results show that the isentropic efficiency of the redesigned vaneless counter-rotating turbine under the design condition has increased by 0.9% and the efficiencies under the off-design conditions are also improved significantly. On the original design, a group of compressional waves are created from the suction surface after about 60% axial chord in the high pressure turbine rotor. While on the new design the compressional waves are eliminated. Furthermore, on the original design, the inner-extending waves first impinge on the next high pressure turbine rotor suction surface. Its reflection is strong enough and cannot be neglected. However on the new design the inner-extending waves are weakened or even eliminated. Another main progress is that the redesigned high pressure turbine rotor is of practical significance. In the original rotor, a part of the blade (from 60% axial chord to the trailing edge) is thin leading to the intensity problem and difficult arrangement of the cooling system. In the new design, however, the thickness distribution of the rotor airfoil along the chord is relatively reasonable. The intensity of the rotor is enhanced. It is possible to arrange the cooling system reasonably.
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".