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
I've been using FLORIS version 2 due to the inability to specify heterogeneous wind directions in later versions. Looking at the code, it seems that when optimizing under wind direction uncertainty, the baseline wind direction is taken as the first wind direction (self.floris.farm.wind_map.input_direction[0]), ignoring any specified wind direction heterogeneity.
In floris.tools.floris_interface.py::get_turbine_power, I see the following:
Is this something the team is aware of? Would there be a benefit to submitting a PR to resolve the issue, or are changes no longer being made to version 2?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been using FLORIS version 2 due to the inability to specify heterogeneous wind directions in later versions. Looking at the code, it seems that when optimizing under wind direction uncertainty, the baseline wind direction is taken as the first wind direction (
self.floris.farm.wind_map.input_direction[0]
), ignoring any specified wind direction heterogeneity.In
floris.tools.floris_interface.py::get_turbine_power
, I see the following:A possible solution is this following:
Is this something the team is aware of? Would there be a benefit to submitting a PR to resolve the issue, or are changes no longer being made to version 2?
Beta Was this translation helpful? Give feedback.
All reactions