More flexibility when writing restart files #372
Comments
marshallward
pushed a commit
that referenced
this issue
Jul 12, 2023
As described in issue #372, I would like to be able to create restart files that contain information about the particle location. These files will be written at the same time as other restart files. I cannot add these calls directly to the driver, because the driver does not have information about the particle location. We have added save_MOM6_internal_state as a subroutine in MOM.F90, and we added calls to this subroutine from each of the drivers. We hope this will allow for more new packages to write restart files in the future. Co-authored by Spencer Jones <spencerjones@tamu.edu>
|
I believe this has been addressed; we now have a clear space for generalizing restarts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment,
save_restartis called directly by the drivers, e.g. here. I would like to option to save non-standard restart files that contain particle locations, but I cannot currently do so without writing new code in all of the drivers (which doesn't seem ideal).I would like it if the driver could call a new subroutine that we could add to
MOM.F90, and that subroutine could callsave_restart. Then any extra steps in the save_restart process could be added only in one place in the code. This would help me directly, but is also likely to help others who might want to add to the code in the future.I talked to @adcroft about this several months ago. He seemed to be on board with the idea. I am posting here to create a paper trail and to start a discussion on whether/how to make this happen.
The text was updated successfully, but these errors were encountered: