Closed uvchik closed 4 years ago
Thanks for testing and spotting! @christian-rli please fix this and document here: https://github.com/OpenEnergyPlatform/data-preprocessing/issues/28
@christian-rli could you please just remove the line, because this bug can make the windpowerlib unusable. Most users will not be able to fix it.
For the future we should think of how to avoid such issues.
I removed the line by hand since @christian-rli is not available this week.
We could add a column verified
to the table. In the windpowerlib we will only use turbines with verified is True
by default. If you want to use a not verified turbine you have to pass a special parameter like verified_only=False
. So a corrupt data set will not break the windpowerlib but if you want to use a new data set it is still possible. If everything is fine we can set verified to true
.
I removed the line by hand since @christian-rli is not available this week.
Thank you @Ludee :+1:
That's a good idea. Another idea is to validate the data in the windpowerlib when importing.
That's a good idea. Another idea is to validate the data in the windpowerlib when importing.
I think we should do both. The windpowerlib should not be vulnerable by corrupt data sets and the oep should make sure that it does not provide corrupt data.
I addressed this issue in PR #101 and added an issue in the OEP-repository.
The turbine with turbine_id 152 in supply/wind_turbine_library is corrupt:
In
power_curve_wind_speeds
you will find duplicate values causing errors in the data processing of the windpowerlib as the windspeed are used as columns.