-
Notifications
You must be signed in to change notification settings - Fork 118
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
FMS2_IO: correcting restart reads in remap_restarts #367
base: main
Are you sure you want to change the base?
Conversation
…art and not read_data
@@ -253,10 +253,6 @@ subroutine fv_restart(fv_domain, Atm, dt_atmos, seconds, days, cold_start, grid_ | |||
!This call still appears to be necessary to get isd, etc. correct | |||
!call switch_current_Atm(Atm(n)) !TODO should NOT be necessary now that we manually set isd, etc. | |||
|
|||
!--- call fv_io_register_restart to register restart field to be written out in fv_io_write_restart |
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.
Much appreciated clean-up.
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.
Minor question regarding existence flag for variables.
…ing of some remap restart fields in fv_io.
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.
lgtm. Is there a test case for this?
@bensonr no I do not have a test case for this |
Description
The reading of restarts in the fv_io.F90
remap_restarts
subroutine was mistakenly using read_data (fms2_io) rather than read_restart (fms2_io). This led to the issues seen in issue #204. This PR corrects this issue.Fixes #204
How Has This Been Tested?
Tested on Gaea with regression tests
Checklist:
Please check all whether they apply or not