workaround for crx2rnx generating a different uncompressed file when it already exists#226
Merged
Conversation
plutonheaven
approved these changes
May 23, 2026
Collaborator
|
@jtec, we may want to have a look at https://github.com/valgur/hatanaka for direct integration of hatanaka decompression in our code (and profiling)? |
Owner
Author
Sounds great: #227 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For whatever reason,
CRX2RNXgenerates a RINEX file with a slightly different number of epochs when the uncompressed file already exists, i.e. calling the tool twice generates different files. I don't know why this popped up now, so this is only a workaround until I figure out what happens there.