FVW: Fix notification about wake extent#3296
Open
luwang00 wants to merge 2 commits intoOpenFAST:rc-5.0.1from
Open
FVW: Fix notification about wake extent#3296luwang00 wants to merge 2 commits intoOpenFAST:rc-5.0.1from
luwang00 wants to merge 2 commits intoOpenFAST:rc-5.0.1from
Conversation
hkross
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is ready to be merged
Feature or improvement description
Previously, notification about FVW wake extent was based on the AeroDyn time step instead of OLAF time step, causing the notification to show up too early if OLAF time step is larger. This bug is now fixed. The logic for the notification is also streamlined, and the duplicated notifications are fixed.
Impacted areas of the software
OLAF
Test results, if applicable
No change to results.