-
Notifications
You must be signed in to change notification settings - Fork 195
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
Checkpointing, NetCDF, and golden master tests #140
Merged
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
001c2d9
Checkpointer constructor with kwargs.
ali-ramadhan f66808f
Fixed bug with filename function for ::Checkpointer.
ali-ramadhan 774a181
Fixed FFT plan reconstruction during checkpointing.
ali-ramadhan e62c8c2
Basic checkpointing test.
ali-ramadhan 755000c
Cooling disk temperature forcing function.
ali-ramadhan fdaa3d7
Set forcing functions to nothing when restoring.
ali-ramadhan 205aec8
Thermal bubble checkpointing test works!
ali-ramadhan a3bdf43
Saving velocity fields at xC, yC, zC.
ali-ramadhan 5b3fc4c
NetCDF thermal bubble integration test.
ali-ramadhan b880a9b
Forgot to commit the actual test.
ali-ramadhan 8786ac3
Forgot to describe the NetCDF integration test.
ali-ramadhan 34fca53
Thermal bubble golden master test.
ali-ramadhan ae3e5ba
Thermal bubble golden master checkpoint file.
ali-ramadhan 5dfbb4f
Adding Random to manifest.
ali-ramadhan dca7290
Deep convection golden master test.
ali-ramadhan a8b6b6c
Deep convection golden master checkpoint file.
ali-ramadhan 3b16880
Updating environment project manifests.
ali-ramadhan 0d132d1
Golden master output is now stored as NetCDF.
ali-ramadhan 354ab07
Merge branch 'master' into system-tests
ali-ramadhan 5d6cec8
Fixed missing async kwarg for NetCDFOutputWriter constructor
ali-ramadhan 371af73
Skipping deep convection golden master test.
ali-ramadhan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Why do we save FFT plans?
It makes sense that a user should plan new FFTs if they are going to run a model, even if they are restarting a checkpoint on the same computer.
@christophernhill what do you think?
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 don't. We set
model.poisson_solver = nothing
before checkpointing then reconstruct the FFT plans afterwards.So you're saying the user should be manually planning the FFTs themselves?