Complete multi-dim code

[paulf81]

Complete multidim code

This issue picks up from issue #785 and proposes a set of steps to finish this work.

Proposed solution

Recommend to take the following steps (can iterate as we go):

• Add example of applying multi-dim code to vary power by TI
• Add tests of this same functionality
• Include example of going to multidim via code versus from specially setup yaml
• Add tests of same functionality?
• Beef up a little bit multidim documentation
• Check that single indexing dimensions work (currently, they don't Bug with multi-dimensional Cp - Ct table #1118)

[misi9170]

I'm working on this over on #996 . Generally speaking though, the multidimensional turbine code is not set up to take the turbulence_intensities keyword argument to FlorisModel.set() and pipe it through to the multidimensional power/thrust_coefficient table. Rather, the multidimensional power/thrust_coefficient table takes arbitrary keywords ("dimensions"), one of which could be "turbulence_intensity", "TI", etc. Those need to be specified separately to the turbulence_intensities passed to FlorisModel.set(). However, I've made setting the multidim_condition easier on #996 by allowing the user to specify it as a keyword argument to set(), for example:

fmodel.set(multidim_condition={"TI": 0.05}) # Assumes that TI is a column of the `power_thrust_data_file`

[paulf81]

This solution makes sense!

[misi9170]

Addressed in #996