Skip to content
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

Closed
chrisbillowsMO opened this issue Dec 23, 2024 · 8 comments · Fixed by #2658
Closed

Revise the user-config.yml to support updated MO user config requirements #2628

chrisbillowsMO opened this issue Dec 23, 2024 · 8 comments · Fixed by #2658
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@chrisbillowsMO
Copy link
Contributor

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.

@chrisbillowsMO chrisbillowsMO added the enhancement New feature or request label Dec 23, 2024
@chrisbillowsMO chrisbillowsMO self-assigned this Dec 23, 2024
@chrisbillowsMO chrisbillowsMO added this to the v2.12.0 milestone Dec 23, 2024
chrisbillowsMO added a commit that referenced this issue Jan 14, 2025
@rswamina
Copy link

@chrisbillowsMO - Does this include the location of the CMOR-ized TerraFIRMA overshoot data (simulations) on JASMIN?

The location is : gws/nopw/j04/terrafirma/MOHC/UKESM1-2/

Thanks!

@sloosvel
Copy link
Contributor

sloosvel commented Feb 4, 2025

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.

@chrisbillowsMO chrisbillowsMO modified the milestones: v2.12.0, v2.13.0 Feb 4, 2025
@chrisbillowsMO
Copy link
Contributor Author

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.

@ehogan
Copy link
Contributor

ehogan commented Feb 7, 2025

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? 🤞

@ehogan ehogan modified the milestones: v2.13.0, v2.12.0 Feb 7, 2025
@sloosvel
Copy link
Contributor

sloosvel commented Feb 7, 2025

Do you think you can have it merged by Tuesday afternoon? If so, it should be ok.

@ehogan
Copy link
Contributor

ehogan commented Feb 7, 2025

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 💪

@ehogan
Copy link
Contributor

ehogan commented Feb 11, 2025

@chrisbillowsMO - Does this include the location of the CMOR-ized TerraFIRMA overshoot data (simulations) on JASMIN?

The location is : gws/nopw/j04/terrafirma/MOHC/UKESM1-2/

Thanks!

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? 😊

@rswamina
Copy link

That's fine @ehogan . I have an issue open already. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants