REF recipe CRE with CMIP7 data

[hb326]

Description

Recipe update (and tests) to work with CMIP7 data and the CMIP7 time range, and using the obs4MIPs version of the CERES-EBAF observations.

• Closes Create fake CMIP7 data for recipe_ref_cre.yml #4445

---

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

[bouweandela]

I noticed there is a version CERES-EBAF-4-2-1 available on ESGF too now. Not sure how that differs from CERES-EBAF-4-2.

[bouweandela]

I tested this recipe with the ref in Climate-REF/climate-ref#683 and it seems to work fine.

[hb326]

I noticed there is a version CERES-EBAF-4-2-1 available on ESGF too now. Not sure how that differs from CERES-EBAF-4-2.

Let me check that quickly. I have just seen that new dataset as well.

[hb326]

Something fishy is going on...
I tested the recipe again with CERES-EBAF-4-2 data and it crashed with the error message:
ValueError: "valid_min" is not of a suitable value (0.00000)

The recipe ran last week just fine with the updated main branch of ESMValCore.
Then I tested the recipe with CERES-EBAF-4-2-1 data, and the recipe ran through fine. However, the data look funky. The data for "swcre" is totally different then the model, and when I look at the header of the preprocessed file, there is a "valid_min" value added that cuts of the data at "0.0" which removes all the data that is supposed to be negative...

netcdf obs4MIPs_CERES-EBAF-4-2-1_swcre_2002-2021 {
dimensions:
lat = 180 ;
lon = 360 ;
bnds = 2 ;
variables:
float swcre(lat, lon) ;
swcre:_FillValue = 1.e+20f ;
swcre:long_name = "TOA Shortwave Cloud Radiative Effect" ;
swcre:units = "W m-2" ;
swcre:positive = "down" ;
swcre:valid_max = 600.f ;
swcre:valid_min = 0.f ;
swcre:cell_methods = "time: mean" ;
swcre:coordinates = "time" ;
double lat(lat) ;
lat:axis = "Y" ;
lat:bounds = "lat_bnds" ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
double lat_bnds(lat, bnds) ;
double lon(lon) ;
lon:axis = "X" ;
lon:bounds = "lon_bnds" ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
double lon_bnds(lon, bnds) ;
double time ;
time:bounds = "time_bnds" ;
time:units = "days since 1850-1-1 00:00:00" ;
time:standard_name = "time" ;
time:long_name = "time" ;
time:calendar = "standard" ;
double time_bnds(bnds) ;

Did we do something weird in the ESMValCore fix, @bouweandela?

[hb326]

Ok. All is fixed now again. Thanks @schlunma!
The recipe runs fine also with CERES-EBAF-4-2-1 data. This is the dataset that can be pushed to REF. It runs until 2025.

[axel-lauer]

Looks good!