Buffering & Aligning Support#114
Merged
Merged
Conversation
This task gets several inputs and aligns a matching window of time for all of them.
This will be a common pattern to have a partially filled spot on a message that has been preallocated.
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
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.
This builds a Copper task that can buffer in circular buffers messages in an arbitrary number of streams and align them in time according to a policy/parameter.
The first implementation just gets a window of time you need as an output and a "time horizon" for when you consider the data stale.
The first use case for this component is to build a 360 view out of combined output from Lidars but it should be generic enough to fit most of your sensor alignment cases.