Update REF ENSO recipes for CMIP7

[flicj191]

recipes:

• ref/recipe_enso_basicclimatology_CMIP7.yml
• ref/recipe_enso_characteristics_CMIP7.yml

updates:

• update to reading CMIP7 data
• update enso diagnostic scripts to include CMIP7 for models
• include dive downs for metrics and extend captions for plots
• update pr obs to GPCPv3.3
• edit preprocessers to not mask land for tos variable, as not required
• use TROPFLUX v2 for tos and tauu to extend to 2021

Still required:

• waiting on v2 of TROPFLUX that will extend to 2025 for variables tos and tauu
• could use another dataset such as ERSSTv5 (tos) or NCEP-DOE-R2 (tauu)?

Data for running:

/scratch/b/b382919/CCCma/ which can be moved to the /MIP-DRS7/CMIP7/CMIP directory
and /scratch/b/b382919/TROPFLUX which is version2, OBS6, Tier2

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🛠 This pull request has a descriptive title
• 🛠 Code is written according to the code quality guidelines
• 🛠 Documentation is available
• 🛠 Tests run successfully
• 🛠 The list of authors is up to date
• 🛠 Any changed dependencies have been added or removed correctly
• 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

• 🧪 Recipe runs successfully
• 🧪 Recipe is well documented
• 🧪 Figure(s) and data look as expected from literature
• 🛠 Provenance information has been added

---

To help with the number of pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[hb326]

@flicj191: could you let @schlunma know where you have stored your fake CMIP7 data so that he can put them in the common CMIP7 data pool on Levante? If we have the data, we can test the recipe as part of the review process.

Thanks!

[flicj191]

@flicj191: could you let @schlunma know where you have stored your fake CMIP7 data so that he can put them in the common CMIP7 data pool on Levante? If we have the data, we can test the recipe as part of the review process.

Thanks!

No problem @schlunma I have transferred to here on Levante: /scratch/b/b382919/CCCma/
This would be in the /MIP-DRS7CMIP7/CMIP directory for your root cmip7 data

[rbeucher]

Hi all — we’re getting ready for the next ESMValTool release, version 2.15, and are planning to freeze the code on 26 June 2026.

Could you please let us know whether you think you’ll be able to finalise the work in this PR by then? If not, no problem — it would just help us plan what can realistically make it into the release.

@flicj191 tagging Felicity for visibility.

[schlunma]

@schlunma I have transferred to here on Levante: /scratch/b/b382919/CCCma/ This would be in the /MIP-DRS7CMIP7/CMIP directory for your root cmip7 data

Just copied the data to our pool (/work/bd0854/DATA/ESMValTool2/CMIP7_DUMMY_DATA). Sorry for the delay!

[flicj191]

Have tested all these impacted recipes and ran successfully:

• recipe_enso_characteristics.yml
• recipe_enso_climatology_level2_3.yml
• recipe_enso_divedown910_1415.yml
• recipe_enso_feedback.yml
• recipe_enso_climatology1.yml
• recipe_enso_divedown11_13.yml
• recipe_enso_feedbacknhf.yml
• recipe_enso_teleconnection.yml
• ref/recipe_enso_basicclimatology_CMIP7.yml
• ref/recipe_enso_characteristics_CMIP7.yml