Adding WebSocket Controller #243
Draft
Conversation
This file contains hidden or 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
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.
This PR introduces a WebSocket controller as well as a React-based frontend which was made as part of a seminar at the DOS-group.
The WebSocket controller follows the same structure as other logging controllers from within Vessim, allowing for a drop in replacement. Messages are sent on
tcp/0.0.0.0:5000via the Socket.IO protocol to all subscribed clients, including the entire grid as well astime,p_deltaande_deltawhich are serialized into a json structure.The frontend client is a React-application displaying all available information in real-time via the aforementioned Socket.IO connection.
TODO:
pyproject.tomlWebSocketcontroller