Remove broken opal node-type #824
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Steffen Vogel <[email protected]>
stv0g
force-pushed
the
node-opal-remove
branch
from
2ab4a31 to
df04257
Compare
|
Can you somewhere link to an alternative? e.g. an example for how to talk to OPAL via UDP? |
Sure, this is already documented in the VILLAS documentation:
I also have an open PR in the documentation repo, which I want to merge as soon as the broken code is removed: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
opalnode-type implementing support for running VILLASnode itself as a asynchronous process in OPAL-RT's RT-LAB simulation environment is currently broken and not functioning anymore.I am proposing to remove this node-type. A new revised integration into OPAL-RT's simulation environments via the Orchestra framework is currently being stabilized.