Dynamic Performance Simulation of an Aeroderivative Gas Turbine Using the Matlab Simulink Environment
Bibliographic record
Abstract
In fossil fuel applications, such as air transportation and power generation systems, gas turbine is the prime mover which governs the aircraft’s propulsive and the plant’s thermal efficiency, respectively. Therefore, an accurate engine performance simulation has a significant impact on the operation and maintenance of gas turbines as far as reliability and availability considerations are concerned. Current trends in achieving stable engine operation, reliable fault diagnosis and prognosis requirements do motivate the development and implementation of real-time dynamic simulators for gas turbines that are sufficiently complex, highly nonlinear, have high fidelity and include fast response modules. This paper presents a gas turbine performance model for predicting the transient dynamic behavior of an aeroderivative engine that is suitable for both mechanical drive and power generation applications. The engine model has been developed in the Matlab/Simulink environment and combines both the inter-component volume and the constant mass flow methods. Dynamic equations of the mass momentum and the energy balance are incorporated into the steady state thermodynamic equations. This allows one to represent the engine model by a set of first order differential and algebraic equations. The developed Simulink model in an object oriented environment, can be easily adapted to any kind of gas turbine configuration. The model consists of a number of subsystems for representing the gas turbine’s components and the thermodynamic relationships among them. The components are represented by a set of suitable performance maps that are available from the open literature. The engine model has been validated with an established gas turbine performance simulation software. Time responses of the main variables that describe the gas turbine dynamic behavior are also included. The proposed gas turbine model with its dynamic simulation characteristics is a useful tool for development of real-time model-based diagnostics and prognostics technologies.
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.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.004 | 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".