Stop OpenFAST for Simulink simulation when trim solution has been found. #930
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
2 tasks
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.
Feature or improvement description
This code tells Simulink to end an OpenFAST simulation after a trim solution has been found when running FAST_Library. Before this change, the code would continue to run to the final analysis time and many additional linearization files could be written.
Related issue, if one exists
Fixes a secondary problem mentioned in #738
Impacted areas of the software
Simulink interface, FAST_Library (perhaps the C++ interface?)
Additional supporting information
This would be noticeable only when using OpenFAST for Simulink with linearization and trim-solution options turned on.
Test results, if applicable
This will not change any test results.