updating and testing the new GPCP v3.3 obs4MIPs dataset

[hb326]

Description

In this pull request the new obs4MIPs dataset from GPCP (v3.3) is tested so that it can be used for REF.
The adjustments are done in a REF recipe.

The new obs4MIPs data for GPCP is available on Levante here:
/work/bd0854/DATA/ESMValTool2/download/obs4MIPs/GPCP-V3.3/v20260220/

At the moment the recipe fails due to problems with the data types after the preprocessing was done.

• Closes #issue_number
• Link to documentation:

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

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

New or updated data reformatting script

• 🛠 Documentation is available
• 🛠 The dataset has been added to the CMOR check recipe
• 🛠 The dataset has been added to the shared data pools of DKRZ and Jasmin by the @ESMValGroup/OBS-maintainers team
• 🧪 Numbers and units of the data look physically meaningful

---

To help with the number of pull requests:

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

[hb326]

@bouweandela: here is the recipe, as discussed.

[bouweandela]

The crash happens because the valid_max attribute is of dtype np.float64 after preprocessing, while the data dtype is of dtype np.float32. I suspect this is caused by the esmvalcore.preprocessor.convert_units preprocessor function.

[bouweandela]

To test, you need to change the branch on this line

ESMValTool/pyproject.toml

Line 307 in 7f334fb

"ESMValCore" = { git = "https://github.com/ESMValGroup/ESMValCore.git", branch = "main" }

to drop-range-attrs and then run pixi lock and then pixi run -e esmvalcore-dev esmvaltool run ref/recipe_enso_basicclimatology.yml

[katjaweigel]

Testing ...

[katjaweigel]

"ESMValCore" = { git = "https://github.com/ESMValGroup/ESMValCore.git", branch = "main" }

Thanks! (I want mamba back) Actually merged drop-range-attrs into main, but I guess I forgot that I have only the main ESMValCore installed and not a custom one so I need to change that ...

[bouweandela]

If you to use your local ESMValCore clone, you can follow the instructions in the docs to set that up: https://docs.esmvaltool.org/en/latest/quickstart/installation.html#using-the-development-version-of-the-esmvalcore-package

[katjaweigel]

Yes, thanks, works now with GPCP V3.3.