IMU Rate Visualization #582
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
|
Can one of the admins verify this patch? |
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 adds a visualization to the result report that includes the sampling rate over the whole dataset for the IMU.
This can allow insight into the "quality" of the IMU and if there are any timestamp problems.
For example, the following IMU has incorrect timestamps where a burst of IMU are send at a rate of 1ms with gaps of 6ms between.
A "good" timestamp would be on that has a fixed rate (aside from sensor drops) such as this one which has a fixed 5ms (200Hz) between readings:
While other IMUs can have "jitter" where alternating readings have small errors around the fixed frequency.
This isn't as big of a problem, but is a source of error (not as bad as having the first example)