Jpl gh 286 #290
Merged
Jpl gh 286 #290
Conversation
This file contains 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
Signed-off-by: Guillaume W. Bres <[email protected]>
- a new --jpl-bpc option is introduced in RINEX-Cli
Which always requires internet access and IS THE ONLY OPTION
to keep the JPL model up to date.
- the local storage is preserved and allows fast deployments
(after a first successful deployment)
- for example, in the past few days the JPL servers have been down.
when deploying without --jpl-bpc:
- the session will rely on the previous JPL model if it was already downloaded.
If this model is too long and servers remain down, you should delete it with!
- the session will rely on low precision (offline) model until a JPL model
has been obtained
When deploying with --jpl-bpc:
- the session will crash because correct network access is expected
Signed-off-by: Guillaume W. Bres <[email protected]>
Signed-off-by: Guillaume W. Bres <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix offline/online deployment options
Which always requires internet access and IS THE ONLY OPTION
to keep the JPL model up to date.
(after a first successful deployment)
When deploying without --jpl-bpc:
If this model is too old and servers remain down, you should delete it !
has been obtained
When deploying with --jpl-bpc: