-
Notifications
You must be signed in to change notification settings - Fork 8
202507 sp3 file discovery #187
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
base: main
Are you sure you want to change the base?
Conversation
… when a file is already downloaded locally
- fix path to new location of sp3.evaluate - minor modifications
… file - rewrote tests - bug corrections (multi-day)
- Work with Path rather than file name (str)
|
I observed that the tests were quite long, which was explained by different things:
I changed many things in the module, and mainly:
And then I rewrote almost all tests, simplifying the test cases. @eulaliesa, you can have a look at the changes between 1534cbe and 3541dac to see those changes. It may feel like I rewrote almost all what you did, but in reality, I could not have done this without your code and our discussions. So thanks a lot! |
|
I still have to merge main into this branch. Will do this later... |
# Conflicts: # src/prx/rinex_nav/evaluate.py # src/prx/rinex_nav/test/test_evaluate.py # src/prx/test/test_main.py
This branch introduces a mechanism to retrieve SP3 and CLK files.
The logic follows a two-step approach:
Local Search:
The system first attempts to find the required SP3 and CLK files locally (e.g. in a pre-downloaded database or directory).
Remote Download with Priority:
If the files are not available locally, it proceeds to download them automatically from known public sources, following a priority list of analysis centers and product types.
Final (
FIN) products are preferred over rapid (RAP) ones, and centers like COD, GRG, and GFZ are prioritized due to their reliability and precision./mgexsubfolder, requiring different path logic during discovery.