Extend statepoint dump feature to support dumps from the last N batches #3655
+334
−26
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.
Description
This MR extends the statepoint dump feature as documented here to support dumping statepoints for last N batches.
Currently, the 'batches' key takes a list of batch numbers for which statepoint files should be saved, for instance: model.settings.statepoint = {'batches': range(5, n + 5, 5)}
this MR extends this to support configuration as:
settings.statepoint = {'batches': [10, 20, 30, -3]}, to write statepoints at specific batches and also keep the last 3 completed
batches (indicated by '-3').
Fixes #3630
Checklist