Issues found in FMI3 configuration of Reference FMUs about reference-fmus HOT 4 CLOSED

@nickbattle, can you make a PR to fix the above problems?

from reference-fmus.

@t-sommer I'm a bit confused by ReferenceFMU versions. At the moment, I'm testing via the master branch of fmi-standard which has a submodule for ReferenceFMUs linked at c40ae3b? That produces fewer errors than the list above, but still has some:

--------------------- Clocks/FMI3.xml
Checking XML
2.2.8 Variable "inClock3" causality/variability/initial/start <input>/<clock>/<exact>/nil invalid at line 16
2.2.8 Variable "inClock3" initial/variability/start <exact>/<clock>/nil invalid at line 16
2.2.8 Variable "inClock3" invalid at line 16
2.2.8 Variable "input2" causality/variability/initial/start <input>/<discrete>/nil/nil invalid at line 24
2.2.8 Variable "input2" invalid at line 24
2.2.1 Variables invalid
2.2.9 Outputs section does not match output variables at line 28
2.2.9 InitialUnknowns must include refs: {1004, 1005, 2001, 2002, 2003, 2004, 2005, 2007}
Errors found.

--------------------- Feedthrough/FMI3.xml
Checking XML
2.2.9 InitialUnknowns must include refs: {3, 5, 7, 9, 12}
Errors found.

The clocks example needs to supply a "start" attribute for inClocks3 and input2, but without knowledge of what these FMUs do, I'm reluctant to "guess" a start value, especially since they are Reference FMUs. The outputs section and initial unknowns are (presumably) less controversial. Who owns these FMUs?

from reference-fmus.

I'm a bit confused by ReferenceFMU versions.

The latest master of the Reference FMUs should implement the latest release of fmi-standard (i.e. v3.0-alpha.5 at the moment). The submodule ref in fmi-standard might not be up-to-date yet.

Who owns these FMUs?

It's a community project. If you make a PR I'll be happy to look over it before we merge it.

from reference-fmus.

How does #61 look?

from reference-fmus.