Modifying trim_iq to add support for optional chnnum #625
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
…ult value from iq structure
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.
This pull request fixes a bug accidentally introduced by #566. That pull request fixed a bug where the
dataarrays iniqdatfiles for some radars were being incorrectly doubled in size (#565). However, I just discovered this caused a new problem for certain radars (probably just the QNX6/MSI-style radars like Fort Hays and Christmas Valley) wheretrim_iqwould only carry over half thedataarray of each record to the output file.To address this, I've added a new (optional)
chnnumkeyword totrim_iqallowing users to override the defaultchnnumvalue in theiqstructure (similar tomake_raw). Note that I've also cleaned up some other line spacing elsewhere intrim_iq.