As a nice to have: It would be good to have an option in the FMIKit to group inputs of fmus according to their names. i.e. "structured variable names" could be used to create bus objects in matlab, as this facilitates the interconnection of the model considerably.
Some tools like targetlink use this mechanism to depict buses in the fmu-xml and some tools like the simulink importer now make this kind of mapping.
In the fmu-xml, this input/output variables are ordered/named for instance as:
This would create two buses at import time with names RearTemperatures and FromTemperatures.
The downside of scripting this by ourselves is that the customers and other proxies need to rely on a separate script to load models. It would be more convinent to have it in the FMIKit itself.
As a nice to have: It would be good to have an option in the FMIKit to group inputs of fmus according to their names. i.e. "structured variable names" could be used to create bus objects in matlab, as this facilitates the interconnection of the model considerably. Some tools like targetlink use this mechanism to depict buses in the fmu-xml and some tools like the simulink importer now make this kind of mapping.
In the fmu-xml, this input/output variables are ordered/named for instance as:
This would create two buses at import time with names RearTemperatures and FromTemperatures. The downside of scripting this by ourselves is that the customers and other proxies need to rely on a separate script to load models. It would be more convinent to have it in the FMIKit itself.