Create a 'load_geometry_from_yaml` function for VortexStepMethod.jl, and run on a simple wing

[jellepoland]

• Work in https://github.com/OpenSourceAWE/VortexStepMethod.jl

• Use a .yaml format similar to: https://github.com/ocayon/Vortex-Step-Method/blob/develop/data/TUDELFT_V3_KITE/config_kite_CAD_CFD_polars.yaml

• Use similar functionality as used in the instantiate method of: https://github.com/ocayon/Vortex-Step-Method/blob/develop/src/VSM/core/BodyAerodynamics.py

• Create rectangular wing from yaml and plot, using csv polar input

• Run aero analysis for the pyramid model

[1-Bart-1]

@ufechner7 created the VSMSettings in src/settings.jl. You should extend the WingSettings in that file with the same fields as you have in your geometry yaml file, and then use the WingSettings struct in the code.

So first read .yaml file content to WingSettings, and then create a constructor for Wing(set::VSMSettings)

[jellepoland]

I decided against extending VSMSettings because:

• VortexStepMethod.jl already uses direct constructors (e.g., RamAirWing(obj, dat)). Extending VSMSettings would break this pattern. It is easier for the user to understand that creating geometries from different file types is handled in the same way.
• I found that adding YAML-specific fields to WingSettings made the file unnecessarily complex.

Instead, I created a file src/yaml_geometry.jl that provides a direct constructor, YamlWing(yaml_file), matching RamAirWing(obj, dat). This results in a clean separation and easy-to-use code:

wing = YamlWing(yaml_geometry_path; n_panels=20, spanwise_distribution=LINEAR)
body_aero = BodyAerodynamics([wing])

[1-Bart-1]

You know that in julia you can create different constructors with the same name, as long as you provide a type in the definition, or they have a different number of arguments?

Wing(yaml_geometry_path::String) # wing constructor from yaml file
Wing(n_panels::Int) # normal wing constructor

[1-Bart-1]

@ufechner7 why do we have the VSMSettings then? Are you planning to implement constructors using the settings?

[ufechner7]

Indeed, all settings must be created from yaml files. Never ever should input data be coded in .jl files. It must be possible for non-programmers to use our models. See: #155

[1-Bart-1]

@jellepoland the ram air wing constructor takes in files, but these are not settings, so this is a different use case. For now, creating a constructor Wing(yaml_path) is fine, but at some point this should become: set = VSMSettings(path), wing = Wing(set)

[jellepoland]

The suggested YamlWing constructor also takes in a file, only now not an .obj but a dedicated YAML file that specifies the geometry. Later .csv files are used containing the aerodynamics 2D polars of each section.

Thanks for pointing out the different constructor options! A question on that topic, @1-Bart-1, if you are suggesting that I write a separate Wing constructor that handles .yaml files, then why is there a separate RamAirWing constructor?