-
Notifications
You must be signed in to change notification settings - Fork 39
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
Revise the user-config.yml
to support updated MO user config requirements
#2628
Comments
@chrisbillowsMO - Does this include the location of the CMOR-ized TerraFIRMA overshoot data (simulations) on JASMIN? The location is : Thanks! |
Hi @chrisbillowsMO , The code freeze for version 2.12 is scheduled for next week on Feb 11th. Do you think you will have time to address this issue for this release? If not, let me know and I will move it to the next milestone. |
Hi @sloosvel - thanks for the message, I've moved the issue to the next milestone. |
Hi @sloosvel 👋 I just discussed this with @chrisbillowsMO and we would really like this in the next release. However, we won't be able to create a PR until Tuesday morning. Would that be ok? 🤞 |
Do you think you can have it merged by Tuesday afternoon? If so, it should be ok. |
Yes! @chrisbillowsMO will work on the PR, I will test on Tuesday morning, @alistairsellar will review, and I will merge in the afternoon 💪 |
Hi @rswamina 👋 This PR is just for changes related to MO paths in the user configuration file. If changes are required to JASMIN paths, would it be possible for you to open a separate issue, please? 😊 |
That's fine @ehogan . I have an issue open already. Thanks! |
MO users now need two alternative ESMValTool configurations.
The proposed solution is to include both specifications in the current
user-config.yml
.I am working on this issue.
The text was updated successfully, but these errors were encountered: