Reference-FMUs
Reference-FMUs copied to clipboard
modelica
Functional Mock-up Units for development, testing and debugging
Support to tune FMU parameters (in modelDescription.xml variability="tunable") during the sim
The results from running 'fmusim' on ModelExchange CoupledClutches FMUs (FMI2 and FMI3) do NOT match the (expected) results from FMPy and the old FMUChecker. The issue is reproducible with both...
Problem: CPU/IO time is mostly spent on writing the result file. Maybe add a `--no-result` option for performance evaluation?
The fmiModelDescription node of the modelDescription.xml could set the version attribute as separate meta data and not merged with the generationTool. Intead of ```xml ``` have ```xml ``` Thanks.
Hello, i am a big fan of the reference fmus, this might be a stupid question, but in model.h the getstring function is defined as Status getString (ModelInstance* comp, ValueReference...
to allow use in external Modelica functions (see https://github.com/modelica/Modelica-FMI/issues/17)
to save CPU time and test the FMU's reliance on other files. see also https://github.com/CATIA-Systems/FMPy/issues/632
Is it possible to include the support for DASSL splver? Currently only [euler|cvode] supported
