rtksvr rtcm ssr: defer using ssr without a matching iode#859
Open
ourairquality wants to merge 1 commit into
Open
rtksvr rtcm ssr: defer using ssr without a matching iode#859ourairquality wants to merge 1 commit into
ourairquality wants to merge 1 commit into
Conversation
If the SSR corrections for a particular satellite are updated with a new IOD before the dependent broadcast ephemeris then the correction becomes invalid and the satellite is dropped from the solution. This can happen across a block of satellites, dropping them all, and frustrates solutions using SSR corrections. RTKLIB already maintains a current and previous ephemeris so can often fill gaps if the ephemeris is updated with a new IOD before the SSR corrections. To avoid breaking a current matching SSR and IODE pair, defer adopting the SSR corrections for a particular satellite if there is not a matching broadcast ephemeris. The update is retried and will proceed after the ephemeris catches up. Initialize the ssr iode to -1 rather than 0, to avoid an unexpected match as 0 is a valid iod.
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
1 participant
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.
Noted satellites not being used when using SSR corrections, and this tries to address one of the issues noted, a mismatch with the ephemeris IOD. Not certain that this is the correction solution, perhaps it's at least an improvement so putting it out there for consideration, and perhaps it could help people exploring SSR corrections if they not similar issues. If your ephemeris are being updated ahead of the SSR corrections then this should not be an issue.
If the SSR corrections for a particular satellite are updated with a new IOD before the dependent broadcast ephemeris then the correction becomes invalid and the satellite is dropped from the solution. This can happen across a block of satellites, dropping them all, and frustrates solutions using SSR corrections.
RTKLIB already maintains a current and previous ephemeris so can often fill gaps if the ephemeris is updated with a new IOD before the SSR corrections.
To avoid breaking a current matching SSR and IODE pair, defer adopting the SSR corrections for a particular satellite if there is not a matching broadcast ephemeris. The update is retried and will proceed after the ephemeris catches up.
Initialize the ssr iode to -1 rather than 0, to avoid an unexpected match as 0 is a valid iod.