You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2021. It is now read-only.
Occasionally, while tracking satellites below some elevation threshold (< 10 deg), momentary observation gaps of a single sample or more for a particular satellite will cause the RTK position solution to jump by some unphysical amount (10s kms within a few sample periods). Sometimes, the discrepancy will be several centimeters. Sometimes, this might cause IAR activity, otherwise not.
Here's an example from a test log at 2015-07-07_20-47-11 for @henryhallam 's ephemeris sanity checks (v0.18-21-gbcf1c76). Here, the SPP solution degrades, but the baseline solution totally chokes. RAIM will probably make this disappear, but this still seems like really buggy behavior.
Occasionally, while tracking satellites below some elevation threshold (< 10 deg), momentary observation gaps of a single sample or more for a particular satellite will cause the RTK position solution to jump by some unphysical amount (10s kms within a few sample periods). Sometimes, the discrepancy will be several centimeters. Sometimes, this might cause IAR activity, otherwise not.
Here's an example from a test log at 2015-07-07_20-47-11 for @henryhallam 's ephemeris sanity checks (v0.18-21-gbcf1c76). Here, the SPP solution degrades, but the baseline solution totally chokes. RAIM will probably make this disappear, but this still seems like really buggy behavior.
The source for this image is here: https://github.com/swift-nav/investigations/blob/master/piksi/fixed2float/v0.19/v0.18-21-gbcf1c76.ipynb
And a closeup of that same time interval:
There are plenty more examples of this@ https://github.com/swift-nav/investigations/blob/master/piksi/fixed2float/v0.19/fixed2float_categorizations_july_5.ipynb.
See also:
/cc @fnoble @imh @henryhallam @kovach @denniszollo @cbeighley
The text was updated successfully, but these errors were encountered: