-
Notifications
You must be signed in to change notification settings - Fork 34
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
Participation in FMU Cross Check #5
Comments
FMIL doesn't provide any master algorithm for simulating arbitrary FMUs, so it's not an "importing tool" (it's just a library). However, if any importing tool that's using FMIL is passing XC, then the used version of FMIL should also "pass". We could perhaps make references in the project README to importing tools that use FMIL, and that are listed in XC. This would not show up in the XC tables though. Any thoughts @iakovn ? |
Hello Filip, you have examples like https://github.com/modelon-community/fmi-library/blob/master/Test/FMI2/fmi2_import_me_test.c where you simulate FMUs. Couldn't you adapt this for the XC FMUS and report the result?? |
I agree with Filip that FMIL that unless we include at least a basic simulation + master algorithm + input/output handling into the library reporting XC results is a bit misleading. I think that we should rather indicate that pyfmi is relying on FMIL when reporting the results to XC in some way. |
@iakovn I think this is reasonable. I'm in favor of indicating that PyFMI relies on FMIL and that the XC results of PyFMI points also to the maturity of FMIL. |
Extend API: check if DefaultExperiment attributes defined
It would be highly beneficial if FMI-Library would participate in the FMI Cross Check https://github.com/modelica/fmi-cross-check. For many tools this has significantly improved the maturity of their FMI support.
The text was updated successfully, but these errors were encountered: