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 pull request is ready to merge.
Feature or improvement description
This pull request resolves an issue where the BeamDyn driver results were different from OpenFAST results. Specifically, OpenFAST failed to converge during initial correction steps whereas the driver succeeded because it didn't perform corrections. It was possible to make OpenFAST converge by specifying a smaller time step which is why the issue wasn't apparent. During the initial correction steps, the
MiscVars
variablevvv
wasn't being reset between steps which caused velocity errors to accumulate and the solution to diverge. This was corrected by re-initializingm%vvv
inBD_InitAcc
which is only called during these initial correction steps.Related issue, if one exists
Impacted areas of the software
5MW_Land_BD_DLL_WTurb
Additional supporting information
Test results, if applicable
The
5MW_Land_BD_DLL_WTurb
regression test results were updated because they were slightly different at the beginning of the simulation. A new test case,5MW_Land_BD_Init
was added to demonstrate that the model converges at a larger time step.