-
Notifications
You must be signed in to change notification settings - Fork 119
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
merge of master into dev/emc #128
Conversation
…cing the necessary functions with fms2_io_mod functions
…name when needed and removing unneccessary code in fv_io_mod
remove trailiing spaces
fixes missing argument in store_data for case where GFS_PHYS macro no…
add in test for do_cube_transform in fv_grid_tool::init_grid
fixes bug in regional bc time calculation in fv_tracer2d.F90
…use fms_mod, only: write_version_number now.
…2beta1 Removing a duplicate use statement of FMS function "write_version_number"
…, addressding Uriel's comments from PR#74
…ter_axis in fv_ada_nudge. Reintroducing flush function and updating namelist read in fv_diag_column
…ation Fms2 io implementation
Adding Issue Templates to Repository
…er resolving merge conflicts
Dev/gfdl updates being brought back to master
Formatted PDF and source files for FV3 documentation.
FV3 Documentation
The changes to tools/external_ic.F90 were not that extensive. For some reason the git system is really munging the comparison unless you ignore whitespace diffs. |
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.
Looks fine to me.
@@ -1583,9 +1162,11 @@ end subroutine read_namelist_fv_core_nml | |||
|
|||
subroutine setup_update_regions |
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.
In a future release we might want to move this routine into fv_nesting.F90
Thanks. We can restore this functionality if there is a desire to do so;
but my understanding is that the tracer distributions on the nest and the
parent match each other closely enough that updating mass fields is
unnecessary.
Lucas
…On Thu, Aug 12, 2021 at 9:27 AM bensonr ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In model/fv_nesting.F90
<#128 (comment)>
:
> + !!! RENORMALIZATION UPDATE OPTION
+ if (neststruct%nestupdate /= 3 .and. neststruct%nestupdate /= 7 .and. neststruct%nestupdate /= 8) then
+
+ endif
+ !!! END RENORMALIZATION UPDATE
@lharris4 <https://github.com/lharris4> - empty if-test removed in
default master branch and pushed to this merge2emc branch
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMUQRVHJPW5B6CYRTIPPD2LT4PD5HANCNFSM5B63URPQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
@XiaqiongZhou-NOAA @junwang-noaa @yangfanglin @DusanJovic-NOAA - can you please take time to review |
! check_nml_error, stdlog,write_version_number,set_domain, | ||
! mpp_clock_id, mpp_clock_begin, mpp_clock_end, CLOCK_SUBCOMPONENT, | ||
! clock_flag_default, nullify_domain</td> | ||
! <td>file_exist, error_mesg, FATAL, check_nml_error, |
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.
file_exist is not used. Maybe it can be removed later
@@ -545,7 +544,7 @@ subroutine fv_control_init(Atm, dt_atmos, this_grid, grids_on_this_pe, p_split) | |||
#ifdef INTERNAL_FILE_NML |
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.
It looks to me the "INTERNAL_FILE_NML" IFDEFs were removed in this file, why do we still need it here?
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.
We do not have any regional nested test, I assume the code changes have been tested in GFDL. I think "INTERNAL_FILE_NML" IFDEF may need further clean up, that can be done later.
Description
Merge of the latest work from GFDL's weather and climate dynamics group contained in default branch to dev/emc branch.
The work includes:
This update CHANGES ANSWERS.
How Has This Been Tested?
Besides exhaustive testing within the GFDL model framework, the UFS RTS has been run. The original runs of the UFS RTS were with certain parts of code reverted to reproduce the original baselines and understand what updates are responsible for changing answers. The only test(s) that fail are ones with gdas listed in their names as the data in the fv_core.res*.nc files appears to have been manipulated and the strict data integrity checks will terminate the run.
Checklist:
Please check all whether they apply or not