use a recent model development run that wasnt 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? N/A
• 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? N/A
• 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)

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)

[ehogan]

Thanks @mo-nikosbaltas 😊

This branch does not need the changes from @NParsonsMO's branch from #324. Please would you create a new branch without the changes from @NParsonsMO's branch, then create a new PR.

(Edited to add that it looks like you might have created your branch from @NParsonsMO's branch, which is why you needed to keep pulling in changes from @NParsonsMO's branch)

[ehogan]

Also, please ensure CMEW runs successfully (specifically the unittest job) before requesting a review.

[mo-nikosbaltas]

Superseded by #350

[mo-nikosbaltas]

Superseded by #350