This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
Auto checkpointing #252
Closed
Auto checkpointing #252
Conversation
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
ferdonline
force-pushed
the
auto_checkpoint
branch
from
76e89ec
to
21eb08a
Compare
|
Closing PR in favor of new ones. Auto-checkpointing might produce too much data. We will consider it maybe at halfway |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is WIP for a possible auto-checkpointing system.
The idea is to from time-to-time automatically create (& overwrite) previous checkpoints, so that in case a simulation fails after a long time not all progress gets lost.
TODO: As an extension to this concept, the coreneuron main could also detect SLURM allocation variables and program a checkpoint when the allocation time is about to expire.