-
Notifications
You must be signed in to change notification settings - Fork 155
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
Release/gfsda.v16.3.0 warnings #464
Release/gfsda.v16.3.0 warnings #464
Conversation
@emilyhcliu |
@aerorahul Please review the warnings from the WRF netcdf/binary interface. Your review and input will be helpful since you were the author of that routine. |
Source code in
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.
I approve the changes in the stubs.
I cannot say about the changes in the monitoring codes.
ctph0 = zero | ||
stph0 = zero | ||
tlm0 = zero |
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.
This is a stub. Meaning, this code exists solely for compilation to succeed in making the handshake.
This routine will not be called at runtime, and if it is, then something is wrong elsewhere.
The values zero
are fine here and possibly serve for suppressing compilation warnings.
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.
There are no run-time errors from this stub routine. They were compilation warnings. NCO wants these warnings to be fixed. Thanks for your review.
ctph0 = zero | ||
stph0 = zero | ||
tlm0 = zero |
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.
same comment as above.
ctph0 = zero | ||
stph0 = zero | ||
tlm0 = zero |
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.
and here.
Regarding the changes to A check of the history of |
@RussTreadon-NOAA Thanks for your suggestion. I will comment out the following line in util/CmakeLists.txt:
|
@emilyhcliu , please do NOT comment out
in this PR. It has already been commented out in PR #456. Please consider merging PR #456 before merging this PR into |
@RussTreadon-NOAA Great! Thanks for letting me know. I will undo the fix in the CMakeLists.txt One question: should I still merge the code changes to fix the variable problem declaration in this PR for gfsda.v16.3.0? |
Not yet. I will run a cycled experiment to verify. |
Isn't NCO requiring that we fix the build |
Building and executing |
Second thought on running an experiment to verify. These are changes for regional model (WRF). I have no means to verify the changes. Since this is a stub as mentioned @aerorahul , the changes of adding initial values do not impact run time at all. I think the changes should be OK. |
OK, I will run a global case to make sure the update gsi.x does not change results. |
Thank you. I agree that these changes should not impact global results. A quick test to confirm this is crossing our t's and dotting our i's. |
Adding @EdwardSafford-NOAA for awareness. |
I ran a cycled experiment for 3 cycles with the changes of initializing ctpho, stphi and stlm0 to zero in stub_wrf_binary_interface.f90 and stb_wrf_netcdf_interface.f90. Comparing the control and experiment, there are no impacts on the results regarding the analysis and the downstream forecasts. The gsistat files, gnorms of the analysis, and all forecast pgb files are identical for all three cycles. For enkf part, the observation statistics in the enkf stat files were compared between the control and the experiment for the third cycle. They are identical. The forecast files for ensemble means are also identical. The selected ensemble member forecast files were checked. They were also identical. |
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.
As noted, changes to Conventional_Monitor
routines need to be committed to GSI-Monitor repo. Conventional_Monitor package no longer resides in GSI repo. Given the change to util/CMakeLists.txt
in PR #456, Conventional_Monitor
is no longer built in release/gfsda.v16.3.0
The changes to the two gsi
source code files have been tested in the gsi.x
and, as expected, found to not alter results. The compilation warnings indicate a true oversight in the code. The intent(out)
variables should be given a value. This PR satisfies an NCO implementation requirement that code compilation not generate warning messages.
Approve changes.
Per NCO's request for gfs.v16.3.0 code delivery, we were asked to fix a few warning messages from the compilation of the GSI code. The warnings are listed as the following:
There are two sets of warnings. The first set comes from WRF binary and netcdf intricate. Three variables: ctph0, stph0, and tlm0, were not initialized.
The solution is to give them zeros as initial value.
The second set of warning comes from the conventional data monitoring code. Some of the variables were not declared properly.
The solution is to declare the variables before they are used.
The warnings went away after the proposed fixes.