Contact Details
No response
Is your proposal related to a problem?
The current master branch does not contain a checkpointing-functionality. lettuce 0.2.3 did.
There are several use cases for checkpoints (drive storage of populations (and time/step value) for a state):
- limited runtime on HPC cluster: save state before time limit on cluster for a single job is reached and reload checkpoint in a new job for seamless continuation of simulation
- running multiple simulations from an identical starting point that was created in a prior single simulation
- save state at the end of a simulation to (potentially) continue/elongate later, if necessary
Describe the solution you'd like
implement checkpointing-utility
Describe alternatives you've considered
An alternative would be for each user to implement a checkpointing-utility themselves...
Additional context
This is additional context.
Contact Details
No response
Is your proposal related to a problem?
The current master branch does not contain a checkpointing-functionality. lettuce 0.2.3 did.
There are several use cases for checkpoints (drive storage of populations (and time/step value) for a state):
Describe the solution you'd like
implement checkpointing-utility
Describe alternatives you've considered
An alternative would be for each user to implement a checkpointing-utility themselves...
Additional context
This is additional context.