bring back the old value of ini_pseudo_initial_date #1372
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.
Hi @JanStreffing,
I think you were the one chaging
ini_pseudo_initial_datevalue fromprev_run.general.start_datetoinitial_date. This PR reverts that change.The problem with the change you made is that people like @mathanase trying to run a continuation of a experiment need to manually specify
ini_pseudo_initial_date. If they don't then the restart links have incorrect negative time in their names becauseinitial_dateis used. With the old approach, this people get automatically the correctini_pseudo_initial_datefor simulations that continue from the last date into the future.For simulations that need to continue with those restarts but from a different date (branching of a control run finished in 2850 and starting a historical in 1850), the user would still need to specify
ini_pseudo_initial_datemanually. We could think of a way of actually shorting that problem as well automatically.Note that
ini_pseudo_initial_dateis only used for branchoff restarts.