Add save_MOM6_internal_state subroutine to MOM.F90 and call during restart#375
Conversation
0e5dc7b to
631342b
Compare
|
Since Alistair is one of the authors of this PR, it probably doesn't make sense for him to be a reviewer. Can you assign someone else @marshallward ? |
|
I can review it (hopefully very soon). |
Codecov Report
@@ Coverage Diff @@
## dev/gfdl #375 +/- ##
============================================
- Coverage 38.22% 38.22% -0.01%
============================================
Files 269 269
Lines 76413 76417 +4
Branches 14031 14030 -1
============================================
- Hits 29209 29208 -1
- Misses 41962 41967 +5
Partials 5242 5242
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Hallberg-NOAA
left a comment
There was a problem hiding this comment.
This seems to me like a reasonable solution to the problem with calling the routines to save the restart files for submodules that are known to MOM6 but not to the driver, as discussed in the description of this PR. As noted in the comments in this commit, there is more work to be done along these lines, but this is a viable way-point in the code changes. This can be merged into dev/gfdl in due course, once the pipeline regression testing has passed.
As described in issue mom-ocean#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>
bb924a7 to
08c3a17
Compare
|
Given that this changes the drivers, which needs consultation with the partners, should we just push ahead with the suggested TODO plan and introduce I can work on this and submit it as a PR to this PR. |
|
I'm happy for you to do that @marshallward , as long as it doesn't take months and months. |
|
I've submitted a potential revision to this PR which does the following:
The PR is here for review: cspencerjones#1 It's potentially disruptive, so I expect it needs careful review before merging. If it's too much, then maybe we can leave it for a later date. |
marshallward
left a comment
There was a problem hiding this comment.
We can take this as-is, and the suggested amendments will be handled in a separate PR.
|
Gaea regression: https://gitlab.gfdl.noaa.gov/ogrp/MOM6/-/pipelines/19805 ✔️ |
|
Thanks very much @marshallward !! |
…La_SL if lamult was present (NOAA-GFDL#375)
As described in issue #372, I would like to be able to create restart files that contain information about the particle location. These files should 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 opted to add
save_MOM6_internal_stateas a subroutine inMOM.F90, and to call it from each of the drivers. We hope this will allow for more new packages to write restart files in the future.I have tested these additions for
solo_driverandFMS_cap, but I don't have access to the other drivers, so I haven't been able to test them.cc @adcroft