Enable FLORIS to use changing wind direction and thrust control at the same time

[genevievestarke]

Currently, FLORIS only allows either yaw control or thrust control. In Hercules, changing wind directions come across as yaw directions to FLORIS, which means that thrust control is not allowed to be implemented at the same time. This causes an error in the code, currently.

[paulf81]

I think if you used the "mixed" turbine model you can apply both yaw and thurst:

Here's an example where it's used: https://nrel.github.io/floris/examples/examples_control_types/003_setting_yaw_and_disabling.html

[misi9170]

Thanks @paulf81 ! The operation model is already set as "mixed"---I think the issue here is that, although we don't really ever intend to be yaw misaligning and derating at the same time, some instances of that are creeping through (possibly because we are trying to apply "realistic" yaw actions, which don't instantaneously match the wind direction, while also trying to derate). I'll look into this more, and override the yaw actions if that's the case.

[paulf81]

@genevievestarke @misi9170 could we close this one for v2?

[misi9170]

I think we can close this as long as we accept that in v2, we never want to model yaw misalignments. That would rule out:

• wake steering simulations
• consensus simulations
• simulations where we want to model "realistic" yaw dynamics where turbines are temporarily misaligned as they move to follow changes in wind direction.

I'm OK with that. The clear intention of Hercules v2 is on plant-power-level simulations, i.e. simulations that don't consider wake steering/advanced wind farm controls other than active power control, and where small misalignments are likely to be negligible.

It looks like yaw angles are already not received/handled in the WindSimLongTerm class. I can also make the change to remove the availability of passing yaw angles from WHOC through the Hercules v2 interface.

Of course, handling yaw angles can probably be reintroduced at a later date if we want it in v2.

[paulf81]

That sounds good to me, one idea could be also to add back in alternative wind simulators in the new framework that are appropriate for this, like hooks back to AMR-wind or FAST.FARM. It's on me for having ripped these out, but if instead of woven through the code, AMR/helics are isolated to the wind aspect I think could be brought back in a non-braking way, and re-enable consensus,wake steering type work