Fix for previous NumCorrections "fix" #30
Merged
Conversation
This file contains 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
Previous NREL fix made the code always perform at least 1 correction step.
ghost
mentioned this pull request
Closed
Closed
psakievich
pushed a commit
to psakievich/openfast
that referenced
this pull request
Oct 27, 2023
One more typo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Next time, please either wait for a pull request from me or perform better tests before taking code from my fork and merging it into dev or master.
I have not run the executable generated by openfast because there are input file changes to the certtest cases and no new files have been provided. So, there is a high level of risk involved when merging large code changes.