Add data-switch node
#16
Open
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
Contributor
|
Could you provide an example in the example folder? |
Contributor
|
Could you look into dora-record. I had implemented an asynchronous recorder which I believe is going to be able to handle higher frequency messages. Maybe you could add your logic with dora-record? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This node serves as a data proxy to unify recording and replaying functionalities.
The node operates in one of three modes, controlled by the
MODEenvironment variable:record): Inputs are recorded and serialized into an.mcapfile.replay): Data is replayed from the.mcapfile, discarding inputs from other nodes.disable): Data is forwarded as is.This node can be particularly helpful for debugging purposes.
TODO
The node name should be negotiated.