Consolidate turbine libraries

For simplicity in the setuptools configuration, I created a new turbine library in floris/turbine_library so there is now two instances with the other one in examples/inputs/turbine_definitions. @bayc Let’s think about how to resolve this via setup.py and the package_data keyword.

See #325

[rafmudaf]

@econdon16 alternatively you can supply your turbine definition directly (as in, not in a turbine library directory) using the !include keyword in the input file…

farm:
  layout_x:
  - 0.0
  - 630.0
  - 1260.0
  layout_y:
  - 0.0
  - 0.0
  - 0.0
  turbine_type:
  - !include /your/path/to/raf_20MW.yaml

[rafmudaf]

Good question - I can’t think of how to do this. Can you share a small example of what you’ve tried?

Are you automatically generating FLORIS input files? If so, you could also include the turbine definition directly under turbine_type rather than including the link to the turbine type yaml file.