Closed MarcusBecker-GitHub closed 6 days ago
right?
Yep that's right, but it's on our radar. If this is a priority for OFF, we can work together to address it.
Hey, I am not in need of it at the moment, but I know someone who might want to use it for power tracking soon-ish.
My plan would be to take it into account while designing the interfaces and then close the connection once the time is right.
Would it be safe to assume that the axial induction would then be set similarly to the yaw angles?
fi.calculate_wake(yaw_angles= my_yaw_angles)
becomes
fi.calculate_wake(yaw_angles=my_yaw_angles, axial_induction=my_axial_induction)
where fi is the FLORIS interface
Yes I think that's right. On the back end, FLORIS will have to calculate thrust from axial induction and rather than the current formulation which is the other way around. It will take some thought to integrate it nicely, but it's definitely doable.
Here are some solutions with varying complexity that come to mind:
Are we still planning to add controllers soon?
@tianz1990 Not axial induction control, there are also no plans for tilt yet. However, a collection of yaw steering controllers will be released soon. What type of control are you interested in?
@MarcusBecker-GitHub Thank you for replying this! This is exactly what I want. I am looking for any interfaces for yaw steering controllers. Basically, I am working on a kind of MPC-based steering control.
Need at least a basic controller to apply LUT settings to the turbines. Yaw motion is the main control input, as the FLORIS interface does not support setting the axial induction yet (right?)