1 THE CREATOR OF GASTURB

My name is Joachim Kurzke and I live in Dachau, a small town near to Munich in Germany. I am a gas turbine performance specialist and a hobby programmer. My gas turbine performance expertise originates from my time at the Institute of Flight Propulsion at the Technical University of Munich, and working 28 years in the performance department of the company which is now MTU Aero Engines as well as from cooperation with experts in international working groups (AGARD, SAE, EU Projects). For more than 20 years I presented papers at the annual Turbo Expo and attended every ISABE conference since 2005.
The highlight of my engineering life at MTU was the participation in the EJ200 project (The EJ200 is the engine of the Eurofighter Typhoon). This exciting time began in 1986 during the preliminary design phase. I was at the testbed when in 1989 the very first EJ200 development engine made its successful maiden run - 90% of the design thrust was achieved. Later I was head of the international EJ200 performance working group which consisted of engineers from Rolls Royce (UK), MTU (Germany), FIAT Avio, (Italy) and ITP (Spain). In 1993 I was promoted to head of the MTU performance department.
Programming is my hobby. Algol was my first programming language, FORTRAN the second. At home, for my first PC which I acquired in the late 1980’s, the language of choice was Turbo Pascal because this compiler was cheap, and the resulting executable ran much faster than any program written in Microsoft Basic. The first program which I wrote in my free time was Smooth C, a tool for post-processing the results of a compressor rig test.


2 THE PROGRAM MOPS
In 1976 I joined the performance department of MTU. On the first day in my new office I was told: Forget all what you have learned at the university, here is the “real” life. I believed that – for about two years during which I learned to use the legacy performance code of MTU. This code had severe drawbacks: The input was cryptic (consisting of numbers only), program modifications took a lot of time and were prone to errors because the structure of the code was confusing – at least for an outsider like me. 
My experience, as a user, inspired me to design a new performance program with a less cryptic input. The most important design aim was to make program enhancement and maintenance easy. The new MOdular Performance Simulation program MOPS was well received in the advanced projects department and by the engineers working on test analysis and performance prediction. MOPS became the standard gas turbine performance tool at MTU for nearly 40 years.
By the way, MOPS is the German name for a pug. Wikipedia describes this dog breed by the Latin phrase multum in parvo, or "much in little" or "a lot of dog in a small space". Pug owners say their breed is the ideal house dog. Unlike the dog, MOPS is both flexible and powerful, but difficult to handle. Once I was asked by the head of engine development the simple question: What is the influence of bypass ratio on SFC? It took me several days to come up with a comprehensible answer!


3 THE BIRTH OF GASTURB
My conclusion was: there is a need for a software which can answer such questions more quickly. Data input and output should be easily understandable, and the results should be presented as graphics, whenever this is meaningful. Creating a nice looking and truly user-friendly program on my PC at home became my ambition as a hobby programmer.
Soon I had written my first home-made performance software, using only knowledge from my past at the university and from open literature. I was given permission to install the program on MTU computers where it found much interest among my colleagues and superiors. Since it was a much smaller program than MOPS, it received the nickname MOEPSLE – the German diminutive of MOPS.
In 1991, Professor Dr. Hans Rick from the Institute of Flight Propulsion saw the need for a new German book about gas turbines and flight propulsion. He invited me to be his co-author who would add the industrial perspective to his academic point of view. The head of engine development at MTU gave me permission.
At that time, books with technical content were expected to include a diskette with some software. For me it was clear: MOEPSLE is very well suited for that purpose. The only problem was that nobody outside MTU would recognize the name of the program and its meaning. Therefore, I rebaptized the program GasTurb.
The progress in writing the book of was poor, the advances in the development of the software were satisfactory. Early program versions were only available for my colleagues at MTU and friends, the first publicly available version was GasTurb 5.2. At the Turbo Expo 1995 in Houston, USA I presented the first paper about GasTurb which was entitled “Advanced User-Friendly Gas Turbine Performance Calculations on a Personal Computer” (ASME 95-GT-147).
From 1995 to 2012 I released every two years on average a new version of GasTurb. Each of them was more powerful and more colorful (i.e. had a better GUI) than its predecessor. In 2013 the GasTurb GmbH in Aachen, Germany took over the program versions GasTurb 12, Smooth C 8.2, Smooth T 8.2 as well as the utilities GasTurb Names 12 and GasTurb Details 5.1.
In the following years I introduced the new GasTurb team to the structure of the program and assisted them with integrating an axial compressor mean line analysis tool into GasTurb 13. While writing the book “Propulsion and Power – an Exploration of Gas Turbine Performance Modeling” in the years 2014 to 2018 I got many new ideas for improving GasTurb. These found their way into GasTurb 13 which again is more powerful and colorful than its predecessor.


4 THE GASTURB PHILOSOPHY
Nowadays, GasTurb is known all over the world. Why is it so successful? Because it puts the user in the center, the user is the king! The motto is: serve the king, to make the king’s life easier.
Many other gas turbine performance programs like MOPS, NPSS, GSP and PROOSIS offer libraries with program modules from which users can build their engine model. This approach is incredibly flexible but puts a burden on the user. Since the programmer of such a software does not know the architecture of the engine to be simulated, it is difficult or impossible to automate the typical engineering tasks.
The software architecture of GasTurb is what I call “task oriented”. Select an engine architecture and what you want to do: engine design, study the off-design behavior for steady state or transient, test analysis … You will only see those input and output quantities which are relevant for your problem. There are dedicated GUI’s for many engineering tasks which are very helpful in solving typical simulation problems.


5 RECENT PROGRESS
There is always room for improvement. A customer was recently interested in the simulation of afterburner transients – the GasTurb team in Aachen helped with testing and implementing my ideas into a beta version of the program. Then there was a request for simulating jet engine starting, windmilling and windmill relight. Again, I drafted the necessary code modifications and the GasTurb Team helped with implementation and testing.
The key to starting and windmilling simulations are compressor and turbine maps which include the regions of low speed and pressure ratio. Smooth C 9 and Smooth T 9 will support map extension using correlations hidden in the already known map region. The theory behind the new compressor map extension methodology is described in the paper ISABE-2019-2499 which I presented at the 2019 conference in Canberra, Australia. I intend to publish a similar paper about turbine map extension at the 2020 European Technical Conference of the Global Power and Propulsion Society.

Joachim Kurzke