Skip to content

Conversation

@andrew-platt
Copy link
Collaborator

@andrew-platt andrew-platt commented Dec 11, 2025

Almost ready to merge. See list below

Feature or improvement description
This PR sets WAT_Scalebox = .true., and updates the method for setting the WAT_dXdYdZ parameter with WAT = 1.

  • The recommendation for wake added turbulence (WAT) is to rescale by default with. However the code and test cases were setup with a default for WAT_Scalebox = .false.. This PR changes this default to .true.. Without the rescaling, cases were occasionally appearing where the velocity from the WAT was causing wakes to propagate in the negative direction.
  • When WAT = 1, the discretization in WAT_dXdYdZ is now set to match the high resolution grid if all turbine hi-res domains are identical, otherwise it will fall back to calculating from recommended practices.

Related issue, if one exists
N/A

Impacted areas of the software
This affects the wake added turbulence in FAST.Farm only.

Additional supporting information

Test results, if applicable
Tests will change slightly

Finish before merge

  • update results (as needed)
  • update docs

@andrew-platt andrew-platt added this to the v4.2.0 milestone Dec 11, 2025
@andrew-platt andrew-platt self-assigned this Dec 11, 2025
Copy link
Collaborator

@jjonkman jjonkman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

if different high res grids on turbines, will set to guidance
Also fix a few other things:
- ElastoDyn Types file had an incorrect comment after some prior PR (no functional change, just regenerated)
- summary file writing was accessing farm%WD%p%WAT_k_Def_k_c (etc) for summary file, but WD is an array, so some compilers will segfault.  Changed to WD_InputFileData%WAT_k_Def_k_c
@andrew-platt
Copy link
Collaborator Author

andrew-platt commented Dec 30, 2025

There are changes in the results as the wakes evolve differently.

TSinflow

At time 90 seconds. XY slice at 90 m.

Screenshot 2025-12-30 at 7 11 21 AM

Before: WAT_dXdYdZ = [5,5,5]

Screenshot 2025-12-30 at 7 12 23 AM

After: WAT: DxDyDz set to: 10.170 10.000 10.000 (using high res grid resolution)

Note that the WAT is causing a larger amount of wake deflection in this case than would be expected indicating the default values for k_Def and k_Grad are not well suited to this case. Also note that there are other artifacts in the wake that should be investigated further.

@andrew-platt
Copy link
Collaborator Author

andrew-platt commented Dec 30, 2025

TSinflow_curl

At time 58 seconds. XY slice at 90 m.

Screenshot 2025-12-30 at 7 26 12 AM

Before: WAT_DxDyDz = 5.0, 5.0, 5.0

Screenshot 2025-12-30 at 7 29 05 AM

After: WAT: DxDyDz set to: 10.170 10.000 10.000 (using high res grid resolution)

Very minor differences in the wakes (almost imperceptible after the wake from T1 arrives at T2).

Screenshot 2025-12-30 at 7 30 17 AM

@andrew-platt
Copy link
Collaborator Author

andrew-platt commented Dec 31, 2025

LESinflow

At 48 seconds. XY slice at 90 m.

Screenshot 2025-12-30 at 7 15 21 PM

Before: WAT_DxDyDz 5.0, 5.0, 5.0

Screenshot 2025-12-30 at 7 16 46 PM

After: WAT_DxDyDz 5.0, 5.0, 5.0 (user defined). ScaleBox = .true. introduces very minor changes to results.

@andrew-platt
Copy link
Collaborator Author

Mod_Amb3

Very minor differences appear in the wake velocities (2nd decimal place, values like W1VDisY).

@andrew-platt
Copy link
Collaborator Author

andrew-platt commented Dec 31, 2025

TSinflowADskSED

At T=90 seconds, 90 m height.

Screenshot 2025-12-30 at 8 04 56 PM

Before: WAT_DxDyDz 5.0, 5.0, 5.0

Screenshot 2025-12-30 at 8 05 56 PM

After: WAT_DxDyDz: 10.170 10.000 10.000 and WAT_ScaleBox: .TRUE.

@andrew-platt
Copy link
Collaborator Author

The py_seastate_1 regression test is failing. This is fixed in #3065, which has not been merged yet.

@andrew-platt andrew-platt merged commit 7f5b3a1 into OpenFAST:dev Dec 31, 2025
11 of 12 checks passed
@andrew-platt andrew-platt deleted the b/FF_WAT_scalebox branch December 31, 2025 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants