forked from tomojitakasu/RTKLIB
-
Notifications
You must be signed in to change notification settings - Fork 10
add -safeephemtime flag to convbin/sbp2rinex for stale-eph processing #95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
4d10851
add -safeephemtime flag to convbin/sbp2rinex for stale-eph processing
denniszollo dd83e1a
adjgpsweek_ref: center rollover at +512 instead of +1
denniszollo 4bc78ed
swiftnav: trust SBP full-width 16-bit week directly
denniszollo 30b5e31
rtcm3: factor SAFEEPHEM_STALE_THRESHOLD_S macro
denniszollo f3cfa94
test: add -safeephemtime regression tests to convbin make test
denniszollo 7ae91b4
test: tighten rtcm3 anchor assertion to specific C45 epoch
denniszollo 87a98b0
swiftnav: fix BDS eph.toe construction to GPST gtime_t
denniszollo 2a6bcce
improve error string per copilot
denniszollo b912015
rtcm3: refactor via trace_safeephem_stale helper
denniszollo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add a new command-line argument instead of just requiring the user to specify
-ro SAFEEPHEMTIME(which appears to be how it is implemented internally anyway)? And does it really make sense to call this a "safe" time? I understand that in your specific context, this flag results in the desired behaviour. But for other use cases one could argue that the default behaviour is the "safest". Maybe consider renaming it to something like "NOEPHWEEKWRAP"?