-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible naming problem in esm_tools. #1268
Comments
Adding @mandresm |
Would be great to have an idea what the error message means. The workaround are getting tedious (modifying ocp-tool twice and updating the pool dir multiple times, once with lpjg named oasis fields in oasis files, and another time with correctly named TL159-land variables in oasis files) |
Working on it as for now. Sorry for the delay |
NP, just pointing to the prio issue from our side. Some other workarounds are easier than than this one :) |
Thanks, that is indeed how I interpreted it and it is very useful to understand prios :) I think I have it. Here: esm_tools/configs/setups/awiesm3/awiesm3.yaml Lines 452 to 457 in 89fc2d1
Try changing it to: '${lpj_guess.mygrid}-land->atma':
lag: ${v2a_lag}
seq: ${v2a_seq}
'atma->${lpj_guess.mygrid}-land':
lag: ${a2v_lag}
seq: ${a2v_seq} This generated for me a On an additional note, this logic of building the grid name does not allow you to match the current existing grid esm_tools/configs/setups/awiesm3/awiesm3.yaml Line 291 in 89fc2d1
|
Did this work? |
It did work! Thx. a lot for the help!!! |
The working branch for this error is: feat/awiesm3-3.4_bugfix
In the awiesm.yaml we (with Jan) made the following modifications:
but we got the following error message after the esm_runscript. Until we changed the naming it worked.
The text was updated successfully, but these errors were encountered: