Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Wrap client as FMU #106

Closed
markaren opened this issue Jun 20, 2019 · 3 comments · Fixed by #118
Closed

Wrap client as FMU #106

markaren opened this issue Jun 20, 2019 · 3 comments · Fixed by #118
Assignees
@markaren
Labels
enhancement

Comments

@markaren
Copy link
Member

As suggested in #71 , it would be nice if we were able to wrap one of the clients as an FMU.
This would allow distributed simulation to any FMI compliant tool without modification.

Obvious problem: The modelDescription.xml refers to a specific model.
Solution: Do not provide a modelDescription.xml. Let the user copy it from the target FMU and paste it into the archive we provide.

Similarly the IP and port could be put into a .txt file inside the archive.
@markaren markaren self-assigned this Jun 20, 2019
@markaren
Copy link
Member Author

Received some insights. At the very least, the modelIdentifier has to be changed to reflect the name of the shared library in the proxy FMU. guid should also be modified.

@markaren
Copy link
Member Author

markaren commented Oct 8, 2019

With FMI4j now supporting FMI 2.0 export for Co-simulation, we are one step closer.

@markaren
Copy link
Member Author

I will implement this as part of PR #116 (should be ready in the near future)

@markaren markaren mentioned this issue Sep 21, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markaren markaren

Labels
enhancement
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Proxify NTNU-IHB/FMU-proxy
1 participant
@markaren