-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Wake added turbulence not working in TurbOPark model #909
Comments
I believe #907 may already solve this. |
#906 has now been merged into the develop branch, and will be included in the main branch in the next FLORIS release. With #906, users can now use the updated TurboPark implementation, which avoids this issue if the import numpy as np
from floris import FlorisModel
fmodel = FlorisModel("inputs/turboparkgauss.yaml")
fmodel.set(
layout_x=[0, 1000],
layout_y=[0, 0],
wind_speeds=[9],
wind_directions=[270],
)
fmodel.run()
print(fmodel.get_turbine_TIs()) with inputs/turboparkgauss.yaml updated (to include the Crespo-Hernandez turbulence parameters) to
produces the expected result:
Note, however, that in this case, while the Crespo-Hernandez model is being used to calculate the output level of turbulence intensity, it is not being used within the Still, I believe this achieves the original request; as we will be supporting the |
This issue follows discussion #906 , where @prith-gs pointed out that the TurbOPark model is not correctly adding turbulence to the wake (even when running with the Crespo-Hernandez turbulence model). I believe the issue stems from this TODO item. Essentially, the
area_overlap
computed in theturbopark_solver
is all zeros, so the subsequent lines that compute the wake added turbulence also produce zeros.Steps to reproduce
produces
which is simply the ambient turbulence intensity at both turbines.
Expected output
According to the Crespo-Hernandez turbulence model, we'd expect that the turbulence intensity at the downstream turbine would be higher than the ambient turbulence intensity, i.e.
with
a
> 0.06.Related
The text was updated successfully, but these errors were encountered: