rtkpos: detect code changes per frequency index #518
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 addresses an issue noted with #502 and should unblock that path.
The code is currently limited to one bias per satellite and pair of receiver signals. If one of these signals changes then flag a slip to have the bias reinitialized. Otherwise such changes can throw off the solution.
The expected observation code is initialized when first seen, and typically does not change, but the processing is now robust to signal changes. This initialization accepts different signals at the same frequency index across a system, but just one signal at a time for a particular satellite and receiver per frequency index.