You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposed workaround does not allow us to solve the problem because it simply removes the structured parameters from the list of parameters exposed in the fmu.
We have quite large simulink models, which require parameters arranged in the form of structures. It is difficult, if not impossible, for us to destructure all of the parameters that we wish to expose in the fmu in order to be able to modify them at the time of execution of the generated fmu.
Currently, we are required to use inline parameters mode in order to remove all structured parameters from the list of parameters exposed in the fmu (otherwise, the fmu cannot be loaded into our calculation tools).
We need to recompile the fmu when these structured parameters change values. This is not sustainable for us.
Please, can you fix this bug ?
thanks in advance
Best regards
The text was updated successfully, but these errors were encountered:
Good morning,
This bug relates to the problems already reported in the following issues:
#151
#74
The proposed workaround does not allow us to solve the problem because it simply removes the structured parameters from the list of parameters exposed in the fmu.
We have quite large simulink models, which require parameters arranged in the form of structures. It is difficult, if not impossible, for us to destructure all of the parameters that we wish to expose in the fmu in order to be able to modify them at the time of execution of the generated fmu.
Currently, we are required to use inline parameters mode in order to remove all structured parameters from the list of parameters exposed in the fmu (otherwise, the fmu cannot be loaded into our calculation tools).
We need to recompile the fmu when these structured parameters change values. This is not sustainable for us.
Please, can you fix this bug ?
thanks in advance
Best regards
The text was updated successfully, but these errors were encountered: