Feature/checkpointing wall clock #1914
Draft
+128
−0
Conversation
This file contains hidden or 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
CodersAcademy006
force-pushed
the
feature/checkpointing-wall-clock
branch
from
f209d57 to
b58a6fe
Compare
Author
|
Converted to draft to invite early feedback on the checkpointing hook location |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR extends the existing opt-in checkpointing infrastructure to support
wall-clock–based triggers in addition to solver-step–based triggers.
Checkpoints are written when a configurable wall-clock interval has elapsed,
using the existing NetCDF output and restart-compatible format. The feature is
fully optional, backward compatible, and does not modify solver or physics
behavior.