Only use save_repeat_run_id for dump files #2223
Merged
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
If the save_repeat argument to Solver::outputVars() is false, we are writing a restart file and should never save_repeat the run_id or run_restart_from.
|
clang-tidy review says "All clean, LGTM! 👍" |
ZedThree
approved these changes
Feb 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 a small follow up to #2149 to make sure that we do not save
run_idas a time-dependent variable to restart files whensave_repeat_run_idistrue.If the
save_repeatargument toSolver::outputVars()isfalse, we are writing a restart file and should never save-repeat therun_idorrun_restart_from.