-
-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FMI support? #135
Comments
Yes, we could add support to spit out FMI binaries, but it's not something that has a good use case for because, well, we don't need those binaries to use any solvers from Julia. So I don't plan on working on it unless there's funding attached to it, but of course we'd be happy to have someone donate a PR for FMI export. |
There is some form of FMI support coming. More details coming at JuliaCon time. |
@ChrisRackauckas howdy. I wanted to see about if there was an update as you mentioned regarding JuliaCon... Is FMI finally coming to Julia?!?!?! 😄 |
Yes, you can find some of it documented here: https://help.juliahub.com/JuliaSim/Tutorials/FMUs/ |
I was able to find the documentation in the link, would like to know if "FMUs" is available outside Julia Sim in any package. |
Maybe FMI.jl can be used for your application. |
FMI.jl is open source, import/simulation of FMI2-FMUs is very robust (we are doing the official FMI cross checks). You can use the full DifferentialEquations.jl ODE solver suite to simulate challenging FMUs. Even FMU export is possible, see FMIExport.jl. Robust support for FMI3 is comming soon (for now only protoypical). However, I don't know if there is already a MTK-Interface available somewhere. |
The Functional Mockup Interface is an open standard for model exchange and co-simulation. I feel like any new "modelling environment" should provide export to this "format". Would this have to be provided by MT or by the higher-level tools built around it? I'm leaning towards the former, since the export of the equations and/or the co-simulation binary should clearly be handled by the engine actually handling all that stuff...
The text was updated successfully, but these errors were encountered: