Component-oriented formulation

[RoberAgro]

Refactor code structure (specially axial turbine model) to organize the code around components.

• Specify components in a list in the YAML file
• Each component is specified with its own:
  • Component type and name (name/number to be specified by the user and then used to rename the design variables? Or design variables named automatically based on their index?)
  • Geometry (performance analysis)
  • Design variables (design optimization)
  • Modeling options (loss model, deviation model, etc.
• We should have models for different components
  • Axial cascade
  • Radial inflow impeller
  • Inlet guide vanes
  • Centrifugal impeller
  • Annular duct (diffuser or interspace)
  • Vaned diffuser
  • 90-degree corner
  • Exhaust guide vanes
  • U-turn
  • Volute
• Each component should have its own heuristic function to generate a realistic initial guess base don 1 or 2 parameters.
• Each component should take the inlet state from the component upstream (both for actual computations and for initial guess generation)

The advantages of this approach is that it will be easier to identify the residual equations and design variables of each component and give them meaninful names. Then they can be combined together in a single dictionary and given tot he solvers.

The other advantage is that it will be very easy and flexible to define different turbomachinery topologies by adding/removing components to the configuration file.

It will also be possible to plot each component in the radial-meridional plane.