We got some progress in GasDynCalc. The GUI and main strategy are defined. Some parts have been already implemented. We will continue to work on it. Below there is a GUI of pre-alfa version.


Computational Fluid x-Dynamics (CFxD)
Break the boundaries!
We got some progress in GasDynCalc. The GUI and main strategy are defined. Some parts have been already implemented. We will continue to work on it. Below there is a GUI of pre-alfa version.

We updated manual. The installer for Windows has been added. Now, it can be installed as a usual Windows program. The updated program (ver. 1.0.1) is here.
We started to develop a new code to calculate pipes, valves, measurements elements, etc. connected in one network. It will be able to use for designing pipelines, experimental test cells, HVAC, etc.
We finished alpha version of GTECalc. The code has been verified with university code. There is an integrated help and separate manual in pdf format. It is free to use and download. The program is here.
We verified the calculation of turbojet engine/turbojet engine with afterburner with university student code. The results are slightly similar.
We finished the implementation of input variables verification. We are starting to validate jet engine calculation.
Gas dynamic functions have been implemented. We decided to integrate a new class to check all input parameters. Hopefully, it will not be long. The first structure was only main program. Now it is changing to
main program <-> gdf (gas dynamic functions), enthalpy (enthalpy calculation), inlet (inlet calculation), isa (atmosphere input calculation) and inputcheck (input parameters validation).
We finished to implement a turboprop engine calculation. Now, we try to optimize the code. Firstly, the gas dynamic functions will be implemented, after it we will start to optimize Save, Print, Export functions.
At the current moment, we spent almost 170 hours for GTECalc development. The user manual took around 20 hours. Each engine is around 10 hours, the interface is around 60 hours, the methodology research is 30 hours and testing is 10 hours.
We started to implement a turboprop calculation and prepare the verification cases for all our implementations.