adds overloads to aggregator::determineTimestamp - #40
Open
niniemann wants to merge 13 commits into
Open
Conversation
…required (smurfa teleportation possible)
…orogen-mars into smurfa
…orogen-mars into smurfa
For the stream aligner and transformer to work, access to a timestamp in the message is needed. By default a member variable called "time" is assumed to exist, which is not the case in the objectDetectionMessages. Therefore, overloads to determineTimestamp are provided which correctly access the timestamp in the header of the messages.
niniemann
force-pushed
the
detection-types-timestamp
branch
from
September 10, 2019 12:42
9face33 to
878dfe1
Compare
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
3 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.
For the stream aligner and transformer to work, access to a timestamp in
the message is needed. By default a member variable called "time" is
assumed to exist, which is not the case in the objectDetectionMessages.
Therefore, overloads to determineTimestamp are provided which correctly
access the timestamp in the header of the messages.