You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think you were the one chaging ini_pseudo_initial_date value from prev_run.general.start_date to initial_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 because initial_date is used. With the old approach, this people get automatically the correct ini_pseudo_initial_date for 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_date manually. We could think of a way of actually shorting that problem as well automatically.
Note that ini_pseudo_initial_date is only used for branchoff restarts.
Hi,
I also tried a branchoff experiment with AWICM3. Therefore I tried out the changes in this PR. In general it worked for me for esm_runscript.
But then esm_master comp-awicm3-develop was not running but gave the following error:
Traceback (most recent call last):
File "/work/ba1264/a270089/conda/envs/esm_tools_macv2sp/bin/esm_master", line 33, in <module>
sys.exit(load_entry_point('esm-tools', 'console_scripts', 'esm_master')())
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_master/cli.py", line 113, in main
main_flow(parsed_args, target)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_master/esm_master.py", line 57, in main_flow
complete_setup = SimulationSetup(user_config=user_config)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_runscripts/sim_objects.py", line 113, in __init__
self.config = prepare.run_job(self.config)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_runscripts/prepare.py", line 20, in run_job
helpers.evaluate(config, "prepare", "prepare_recipe")
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_runscripts/helpers.py", line 71, in evaluate
config = esm_plugin_manager.work_through_recipe(
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_plugin_manager/esm_plugin_manager.py", line 159, in work_through_recipe
config = getattr(submodule, workitem)(config)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_runscripts/prepare.py", line 647, in finalize_config
config.finalize()
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/esm_parser.py", line 3305, in finalize
self.run_recursive_functions(self)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/esm_parser.py", line 3331, in run_recursive_functions
recursive_run_function([], config, "atomic", marked_date_to_date_object, config)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/provenance.py", line 1004, in inner
output = func(tree, rhs, *args, **kwargs)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/esm_parser.py", line 2040, in recursive_run_function
right[key] = recursive_run_function(
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/provenance.py", line 1004, in inner
output = func(tree, rhs, *args, **kwargs)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/esm_parser.py", line 2040, in recursive_run_function
right[key] = recursive_run_function(
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/provenance.py", line 1004, in inner
output = func(tree, rhs, *args, **kwargs)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/esm_parser.py", line 2004, in recursive_run_function
right = func(tree + [None], right, *args, **kwargs)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/provenance.py", line 1004, in inner
output = func(tree, rhs, *args, **kwargs)
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_parser/esm_parser.py", line 2643, in marked_date_to_date_object
entry = Date(actual_date, config["general"]["calendar"])
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_calendar/esm_calendar.py", line 265, in __init__
self._init_from_str(indate, calendar=Calendar())
File "/work/ab0995/a270089/esm_tools_macv2sp_dars/src/esm_calendar/esm_calendar.py", line 287, in _init_from_str
date, time = indate2.split("_")
ValueError: too many values to unpack (expected 2)
I tried this with esm_tools, version 6.55.0
What of course workes is setting ini_pseudo_initial_date: "${prev_run.general.start_date}" in my runscript.yaml.
Hi, I also tried a branchoff experiment with AWICM3. Therefore I tried out the changes in this PR. In general it worked for me for esm_runscript. But then esm_master comp-awicm3-develop was not running but gave the following error:
...
I tried this with esm_tools, version 6.55.0
What of course workes is setting ini_pseudo_initial_date: "${prev_run.general.start_date}" in my runscript.yaml.
Hi @nwieters, I could reproduce this issue and I think I have now solved it.
This PR needs to wait for #1329 to be merged to avoid conflicts on the tests (normally not needed but there are some special circumstances around #1329 that result into it blocking other PRs)
This file contains hidden or 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
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.