-
Notifications
You must be signed in to change notification settings - Fork 78
Where to find Reference FMUs? #28
Comments
Comment by cbertsch on 14 Dec 2017 10:57 UTC There is a set of draft reference FMUs available within the FMI project on the internal git repository that have been created by Awad Mukbil and myself and have been presented in https://www.modelica.org/events/modelica2017/proceedings/html/submissions/ecp17132533_BertschMukbilJunghanns.pdf. (I will share them with you so that you can give feedback). Once they have been reviewed and approved within the FMI Project they shall be made available publicly and included in the Cross Check repository. |
Comment by Mihal Brumbulli on 14 Dec 2017 12:10 UTC For the time being, does it mean that, as stated in the same document, an import tool must report only on: |
Comment by cbertsch on 14 Dec 2017 13:37 UTC One prerequisite for the future release of the Reference FMUs is the availability for different platforms. |
@chrbertsch can we just close this issue? |
Yes, please close. |
@t-sommer You probably now have to close, since I don't have rights in fmi-cross-check... |
But the issue still exists or am I missing something? |
I would close the issue and perhaps add somethere (where?) a comment on the XC-rules document , that there do not yet exist released reference FMUs. |
The rules can only be changed once a year (see https://github.com/modelica/fmi-cross-check/blob/master/FMI-CROSS-CHECK-RULES.md#8-changes-to-the-fmi-cross-check-rules). Until then we'll have to leave this issue open. |
Reported by Mihal Brumbulli on 14 Dec 2017 10:19 UTC
Greetings,
In document FMI_Cross_Check_Rules_v3.1_2015_07 page 7 (No 10 in the table) is stated:
"FMU importing tools must report on importing for all Reference FMUs available for the supported FMI Variant and supported platforms provided on the SVN server"
Searching on the public branch I couldn't find an entry marked as "Reference FMUs". Can someone point me to it?
Migrated-From: https://trac.fmi-standard.org/ticket/427
The text was updated successfully, but these errors were encountered: