Use a recent model development run that wasn't produced for CMIP

[mo-nikosbaltas]

Closes #306

PR creation checklist for the developer

• Has <issue_number> above ☝️ been replaced with the issue number?
• Has main been selected as the base branch?
• Does the feature branch name follow the format <issue_number>_<short_description_of_feature>?
• Does the text of the PR title exactly match with the text (not including the issue number) of the issue title?
• Have appropriate reviewers been added to the PR (once it is ready for review)?
• Has the PR been assigned to the developer(s)?
• Have the same labels as on the issue (except for the good first issue label) been added to the PR?
• Has the Climate Model Evaluation Workflow (CMEW) project been added to the PR?
• Has the appropriate milestone been added to the PR?

Definition of Done for the developer

• Does the change in this PR address the above issue / have all acceptance criteria been met?
• Does the change in this PR follow the requirements in the wiki: Developer Guide (including copyrights)?
• Have new tests related to the change been added?
• Do all the GitHub workflow checks pass?
• Do all the tests run locally and pass? (Note: the tests are not run by the GitHub workflow, see wiki: Run the tests locally)
• Has the API documentation (e.g. docstrings in Python modules) related to the change been updated appropriately?
• Has the user documentation (i.e. everything in the doc directory) related to the change been updated appropriately, N/A including the Quick Start section?
• Do the HTML pages render correctly? (See wiki: Build the documentation locally)

PR creation checklist for the reviewer

• Has <issue_number> above ☝️ been replaced with the issue number?
• Has main been selected as the base branch?
• Does the feature branch name follow the format <issue_number>_<short_description_of_feature>?
• Does the text of the PR title exactly match with the text (not including the issue number) of the issue title?
• Have appropriate reviewers been added to the PR (once it is ready for review)?
• Has the PR been assigned to the developer(s)?
• Have the same labels as on the issue (except for the good first issue label) been added to the PR?
• Has the Climate Model Evaluation Workflow (CMEW) project been added to the PR?
• Has the appropriate milestone been added to the PR?

Definition of Done for the reviewer

• Does the change in this PR address the above issue / have all acceptance criteria been met?
• Does the change in this PR follow the requirements in the wiki: Developer Guide (including copyrights)?
• Have new tests related to the change been added?
• Do all the GitHub workflow checks pass?
• Do all the tests run locally and pass? (Note: the tests are not run by the GitHub workflow, see wiki: Run the tests locally)
• Has the API documentation (e.g. docstrings in Python modules) related to the change been updated appropriately?
• Has the user documentation (i.e. everything in the doc directory) related to the change been updated appropriately, including the Quick Start section?
• Do the HTML pages render correctly? (See wiki: Build the documentation locally)

[NParsonsMO]

Agree it runs and produces the requested output.

One copyright change requested.

Few other comments / queries.

[NParsonsMO]

I gather from conversations at planning that it is OK to have the mip table number hard coded in, and I have no reason to believe that 0.0.25 is any worse than 0.0.9, so I will approve.

[ehogan]

Thanks @mo-nikosbaltas 🥳

Please update the PR title to match the issue title (there is an extra "update" at the end of the PR title).

cylc vip -O metoffice -O unittest and cylc vip -O metoffice -O test both work for me 🥳

[mo-nikosbaltas]

OFFICIAL I had responded. OFFICIAL From: Emma Hogan ***@***.***> Sent: 22 January 2026 18:32 To: MetOffice/CMEW ***@***.***> Cc: Nikolaos Baltas ***@***.***>; Mention ***@***.***> Subject: Re: [MetOffice/CMEW] Use a recent model development run that wasn't produced for CMIP (PR #350) @ehogan commented on this pull request.

________________________________ In CMEW/app/unittest/kgo/test_updated_radiation_budget_recipe.yml<#350 (comment)>:

----

+# @mo-nikosbaltas<https://github.com/mo-nikosbaltas> would it be possible for you to respond to this comment, please? 😊 — Reply to this email directly, view it on GitHub<#350 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNX4ZM6TFHSRVBLWLHPP4KT4IEJQTAVCNFSM6AAAAACSKRTAAOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTMOJTHEZTGNBWGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[mo-nikosbaltas]

Reverted config-developer.yml