The structure of the input data should be unified

[ufechner7]

Currently, the input data is partially defined:

• in form of matlab code
• in form of CSV files

Suggestion:

• put all input data that is written by humans into one .yaml file per simulation project, well commented
• in additon, have a folder with .csv files for computer generated tables
• do NOT use csv files that contain just one scalar
• CSV files should be comma separated
• CSV files should NOT contain empty lines
• all CSV files should have a header with the column names

[MarcusBecker-GitHub]

With the current system, the user has a better human interface to some of the settings, which was originally the goal.
However, while practical for individual simulations, this also makes input file generation more difficult.

I agree that this version of FLORIDyn would benefit from a one-input file in a .yaml shape.
Ideally the rework is consistent with OFF and the Julia FLORIDyn version.