Skip to content
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

If the JPL database cannot be accessed, the creation of QcContext will fail when using rinex-cli #286

Open
vicalloy opened this issue Dec 24, 2024 · 1 comment

Comments

@vicalloy
Copy link
Contributor

vicalloy commented Dec 24, 2024

d0602bb#diff-67600567e036bbcbf6e0f241a23a11f60131adb0d7f1d30f3e2e9acd75b8efbd After this commit, creating CGGTTS will fail if there is no network access.

If the JPL database cannot be accessed, meta_almanac.process(true)?; will raise an error, causing the creation of QcContext to fail.

I see that you have added a QcContext::new_almanac, but it is not used anywhere.

Could you add a command parameter to rinex-cli to avoid network access?

@vicalloy vicalloy changed the title If the JPL database cannot be accessed, the creation of QcContext will fail If the JPL database cannot be accessed, the creation of QcContext will fail when using rinex-cli Dec 24, 2024
@gwbres
Copy link
Collaborator

gwbres commented Dec 24, 2024

Hello,

thank you for helping improving our tools once again;

that's exactly what we're trying to avoid actually.. we should always be able to rely on an offline model.
I presume this scenario has not been tested yet, I'll give it a try tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants