-
Notifications
You must be signed in to change notification settings - Fork 151
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
nread bug in read_radar.f90 #738
Conversation
…ero after processing TDR data
There is already an if condition |
Yes. line 368 is to process level2 radar data. Without line255, nread is reset to zero even there is no TDR data. This is one of reason that the value of nread is incorrect after read_radar. |
Understand. Then I have no issue with this change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nread should be the total # of obs that read in (corresponds to nsuper2_in), not the actual # of obs that is kept. Additionally, it makes more sense to use nread=nread+1 inside the superobs loop near nsuper2_in instead of outside the loop.
Additionally, for the if statement, even if using or in the if condition. If the infile is neither 'tldplrbufr' nor 'tldplrso', then integers like noutside would not be initialized (e.g. L2861).
…e different observation type.
Regression tests passed on both Hera and WCOSS2. Hera: 100% tests passed, 0 tests failed out of 7 WCOSS2 100% tests passed, 0 tests failed out of 7 Total Test time (real) = 1735.02 sec |
This PR is to bring read_radar bug fix (#738) committed in the develop branch to RRFS release branch.
Description
In read_radar.f90, the value of nread should be "nsuper2_kept" and shouldn't be reset to zero after processing TDR data.
Resolves #737
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist