Dependency on ModelManagement about faulttriggering

[fvanderlinden]

The FaultTriggering library itself is free to use, and the implementation of the faults itself is tool independant. The only thing in the library which is currently depending on the Modelmanagement toolbox is the Fault finding algorithm.

We are working on an implementation which relies on FMI 2.0 instead of Modelmanagement to make the generation of the fault wrapper tool independant.

Since there is no standardized way using the Modelica language to search through the model tree, I have made an implementation using the Modelmanagement library, as this used to be the only way to search through the model tree using Dymola, the tool I use in daily practice.

The implementation of the faults using the blocks of the library can be done in any tool, only the search algorithm has to be rewritten:
This search algorithm has only 1 function which depend on this library: "FaultTriggering.Utilities.Internal.getAllModelComponents". Furthermore the functions "FaultTriggering.Utilities.Internal.getVariableValues" and "FaultTriggering.Utilities.Internal.getParameterValues" and "FaultTriggering.Utilities.Internal.getVariableMode" use a dymola specific function to get to the default values.

It should not be too much work to upgrade this to FMI 2.0, as FMI 2.0 has the possibility to output an XML file which can be read. This XML file has the complete model structure as well as the default values, which can be directly used.

Unfortunately, I am currently low on time to do this properly making sure no bugs are there, but I hope to get this done in the close future.

[fvanderlinden]

The dependency on ModelManagement is removed. However, as far as I know there is no standardized method for generating FMU's and reading them. Unfortunately therefore still a dependency on Dymola exist.
If a generalized standard is generated, this dependency can be avoided.

[tbeu]

The dependency on ModelManagement is removed.

This holds for the FMI branch only, right?

[fvanderlinden]

I used this comment as an input to finally update all other branches. Therefore, this hold now true for all branches!

On the other hand: I have no clue on how compatible the library is with tools other than Dymola due to the heavy use of scripting to be able to generate a complete library. Unfortunately there exists no standard here.

[fvanderlinden]

Scripting is not supported for any other tool as far as I know. However the library can be used also by users of other tools without the scripting functionality.

As the dependancy of ModelManagement is now gone, I will close this issue.

[tbeu]

FYI: ModelManagement is free of license since Dymola 2017 FD01.