Time accuracy metric #128
Merged
Time accuracy metric #128
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
Time accuracy is reported in ns while position accuracy is in meters. Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
Export time accuracy metric into monitoring data Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
|
So you don't want the millimeters ? (I'm surprised you discard the precision) (also why use 64 bits then ?) |
|
And you don't want to expose the position accuracy via the API ? |
agagniere
approved these changes
Apr 5, 2024
We checked position accuracy values and didn't find them useful. We decided to monitor time accuracy only for our case |
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.
Add dynamic accuracy values to the GNSS monitoring