Release v0.2.0 (due: end of July)

[birgits]

The v0.2.0 will have some API changes:

• no p_nom column in power curve csv file (@SabineHaas)
• name parameter of wind turbine, wind farm and wind turbine cluster as optional (or remove?) (@birgits) --> same for coordinates parameter?!
• remove power_output attribute from wind turbine, wind farm and wind turbine cluster (@birgits)
• remove installed_power attribute (@birgits )
• use efficiency attribute for wake_losses_to_power_curve() instead of wake_losses_model parameter (@SabineHaas)
• remove overwrite parameter from wind_turbine.get_turbine_data_from_oedb() (@SabineHaas)
• remove deprecation warnings (@SabineHaas and @birgits)
• remove fetch_curve and data_source parameters from WindTurbine (@SabineHaas)
• adapt examples (@birgits)
• check if tests are adapted, f.e. no fetch_curve parameter (@SabineHaas)
• csv file containing all turbine data from oedb apart from curves (@SabineHaas)
• Check if example/modelchain_example.ipynb was merged correctly (@birgits)
• document changes in whats new (@SabineHaas, @birgits)

[uvchik]

Thanks to @SabineHaas it is possible to use the windpowerlib offline but for the next major release I would suggest to restructure the API.

As there has been some communication problems in the last month I would suggest to make a breakout group at the next oemof meeting.

[birgits]

Thanks to @SabineHaas it is possible to use the windpowerlib offline but for the next major release I would suggest to restructure the API.

@uvchik can you specify this a bit more? Because if you have the csv vs hdf5 discussion in mind, we are planning to go back to csv in the next release and should therefore talk about this soon (this or the upcoming week). If it's something that can wait until the dev meeting a breakout group sounds good.

[uvchik]

No, it is more about the whole data-base-file-structure. But I really appreciate the change back to csv.

[uvchik]

PR #62 includes my ideas from above.