Conversion of setup to text files

[salmarbas]

Definition of wind farm, turbines, control, wake parameters etc. is now possible in tab-delimited text files.

• Wind farms can consist of turbines with variable type and hub height, as set up in the text table. Hub height has been removed from the turbine type properties, as it is no such (one turbine type, i.e. rotor diameter, rated power, control characteristics etc. is usually offered by manufacturers with different tower heights).
• Greedy control LuTs can be multi-dimensional (dimension 1 are rows, dimension 2 colums, dimension 3 is separated with with a ";" row, dimension 4 with ";;" etc.)
  For this purpose, the interfaces to read the text files have been directly integrated in the class constructors, i.e. the object properties are directly defined from the text file contents. The class constructors are then called directly without additional functions to create the objects (see 'DemoSimulation.m'). A new folder 'setupDefinitions' has been created to cummulate the changed/new classdef/function/settings files.
  Now to define a new setup, distinct text files have to be changed/created in setupDefinitions as desired; there cannot be multiple parallel setups in this folder.

Note that currently the text-defined LuTs can only be used in the greedy control strategy, the project maintainers might have good ideas how the generalize the concept of text input for other control strategies.

[Bartdoekemeijer]

Can one of the admins verify this patch?