Replies: 1 comment
-
A couple ideas I have:
Because Simulink has its own TMax, we decided to override the TMax from the OpenFAST input file, but that could also be modified. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The FAST_Sizes routine in the FAST Library was recently changed so that the calling code could use the TMax specified in the input file (see #962). Previously, the value of TMax given in FAST_Sizes would be used over the value in the input file. In an attempt to preserve both functionalities, #962 added optional arguments to FAST_Sizes. Since this is a C++ feature and not available in C, compiling for Simulink does not work. A workaround is added in #1180 to use the optional arguments when compiling for C++ and maintain the previous API when compiling for C. This is not a sustainable solution since now the API is different depending on the language.
Here are a few key steps in going from
FAST_Sizes
toFAST_init
:I don't have a great idea for handling both behaviors. It seems the feature to use TMax from the subroutine is tied directly to the Simulink functionality, while using TMax from the input file is required for the Python integration to WEIS.
Beta Was this translation helpful? Give feedback.
All reactions