Replies: 1 comment
-
Hi @aclerc , thanks for asking! In my opinion, this type of "practical consideration" for wake steering is probably a little too niche for FLORIS. We've been trying recently to keep FLORIS more general and limit the number of special cases that go in, and my feeling is that this is probably enough of a special case that I'd probably leave it out (but others, feel free to disagree with me). That being said, I think this could be a nice additional feature to FLASC. In FLASC, we have a utility for handling practical modifications to a FLORIS-designed yaw lookup table, which your approach could possibly be added to as a new function. Alternatively, I wonder whether an optimal lookup schedule from FLORIS (formatted as a Dataframe |
Beta Was this translation helpful? Give feedback.
-
I've written some code to check which turbines are wake free (based on criteria in IEC61400-12-1:2017) and only let those turbines steer. I do that by editing the
minimum_yaw_angle
andmaximum_yaw_angle
arrays passed toYawOptimizationSR
and running the wake free check and optimizer one direction at a time. This is particularly useful for designing the look up table for a validation campaign where it's difficult to measure wake steering uplift deep in the wind farm. Just wondering if this is already a feature I've missed? Happy to contribute code related to this if it's useful.Beta Was this translation helpful? Give feedback.
All reactions