problems when processed file shares location with other RINEX files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 9
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 4
Description
I had a problem when my rinex file was in the same folder as other compressed RINEX files (.crx.gz). First, prx decompressed all the files in the folder (not expected), and then some error appeared.
I think this error comes from nav_file_discovery.discover_or_download_ephemerides, where we test all files in folder.rglob("*"). We could be more restrictive here.
A quick solution was to put the processed file alone in a separate folder.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading nav_file_discovery.discover_or_download_ephemerides and reproduce the issue with a processed RINEX file alongside compressed .crx.gz files. Trace the folder.rglob("*") results and verify that unrelated compressed RINEX files are no longer decompressed or included, while the processed file still completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100