feat: automating simulation restarts #516
Open
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 is a WIP to provide a way that automatically and intuitively restarts simulations. We need this feature as our cluster may stop a job when another high-priority job arrives. However, we can let a job be restarted automatically. So the idea here is to have some automatic process that detects that the simulation already ran and then continues at the last possible iteration.
The current implementation does the following:
controller.outputDirectory{output}/restart-X. The first restart will have the index 0, and so on.{output}/restart-Yis found, it will (1) traverse in ordered sequence all the existing restart directories, and (2) traverse all iteration directories in these restart directoriesThis is a proof-of-concept, needs to be tested properly. For now, there are techincally included:
Some additional changes: