User-interface API design

[rafmudaf]

FLORIS user-facing API design development

See #801 and #823 for discussion on .set() and .run().
See #805 for a redesign of the visualization functions.

Additional questions

Calculate Plane functions

#823 introduces a new workflow for changing settings and running the wake calculation. A characteristic flow is:

fi = FlorisInterface(...)
fi.set(yaw_angles=20 * np.ones((fi.floris.flow_field.n_findex, fi.floris.farm.n_turbines)))
fi.run()

fi.reset_operation()  # Reset operation set-points to their defaults
fi.set(layout_x=[0, 0], layout_y=[0, 1000], wind_speeds=[8, 8], wind_directions=[270, 270])
horizontal_plane = fi.calculate_horizontal_plane(height=90.0)

The pattern is set -> run -> post process. However, the calculate_*_plane functions still accept wind direction, wind speed, and operation set-points which deviates from the pattern above.

• How should this API look?
• Is calculate_ still the right name?