AP_GPS: fix SBF BaseVectorGeod double DNU sentinel value#32633
Closed
omarzayedbeshir wants to merge 1 commit into
Closed
AP_GPS: fix SBF BaseVectorGeod double DNU sentinel value#32633omarzayedbeshir wants to merge 1 commit into
omarzayedbeshir wants to merge 1 commit into
Conversation
Open
Contributor
|
hold until the original poster agree to make the fix |
peterbarker
reviewed
Apr 1, 2026
|
|
||
| // just breakout any consts we need for Do Not Use (DNU) reasons | ||
| constexpr double doubleDNU = -2e-10; | ||
| constexpr double doubleDNU = -2e+10; |
Contributor
|
The alternative PR is here #32642 |
Contributor
|
I think this has been resolved by #32642 so closing. thanks very much for the contribution in any case! |
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
4 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.
In the SBF (Septentrio Binary Format) protocol, the Do Not Use (DNU) sentinel value for double-precision fields is -2e+10 (i.e., -2e10), not -2e-10. I, therefore, adjusted the value to be -2e+10.