You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, thank you for sharing the relevant research on wind power prediction.
When I was using your code, I found that the sample data header has two rows. Does this mean that using proprietary data requires adjusting the format to be consistent with the sample data. There is an issue with this. My input may be in units of potential height rather than meters. Will labeling the height in the second row as potential height affect the results.
The text was updated successfully, but these errors were encountered:
Dear @muyeqingfeng, for the weather data it is necessary to specify the height it corresponds to, because e.g. the wind speed data then needs to be extra- or interpolated to the turbines hub height in order to determine the wind speed at hub height for the power output calculation. I don't quite understand, why this would be a potential height? Or did you mean, that your wind turbines have a potential height? In any case, I think that you can call it potential height in your weather and turbine data dataframes without getting an error. I hope this helped.
Firstly, thank you for sharing the relevant research on wind power prediction.
When I was using your code, I found that the sample data header has two rows. Does this mean that using proprietary data requires adjusting the format to be consistent with the sample data. There is an issue with this. My input may be in units of potential height rather than meters. Will labeling the height in the second row as potential height affect the results.
The text was updated successfully, but these errors were encountered: