Update timerange and reference dataset for CMIP7 cloud radiative effects diagnostic#683
Update timerange and reference dataset for CMIP7 cloud radiative effects diagnostic#683bouweandela wants to merge 13 commits into
Conversation
|
@lewisjared When I run the command with this branch it ends with Any ideas on what I'm doing wrong here? |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 6 files with indirect coverage changes 🚀 New features to boost your workflow:
|
|
Running with A downside of having no real test data? |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Resolves the `recipe.py` conflict by taking main's `_ESMVALTOOL_COMMIT`. Main has since converged on 12cb5309, and `ref/recipe_ref_cre_cmip7.yml` now exists at that commit with the sha256 this branch already records in `recipes.txt`, so the branch no longer needs its own pin.
Reworks the diagnostic so both source types share `ref/recipe_ref_cre_cmip7.yml`. - Rewrites the recipe timerange per source type in `update_recipe`: 2002-2014 for CMIP6 and 2002-2021 for CMIP7. The base recipe hardcodes the CMIP7 window, and CMIP6 `historical` ends in 2014. - Replaces the three native references (CERES-EBAF Ed4.2, ESACCI-CLOUD, ISCCP-FH) with the obs4MIPs `CERES-EBAF-4-2-1` reference, declared as a data requirement for both source types and added to the ESGF fetch script. - Fabricates CMIP7 coverage through 2021 in the test case via `extend_historical_to`, because CMIP7 `historical` stops in 2014. - Reverts the ESMValCore pin to main's 2cff15ca. The branch had moved it forward, which the new recipe does not need and which applies to every diagnostic. - Bumps `CloudRadiativeEffects.version` to 2, so both baselines need re-minting.
8e076ac to
31e4d13
Compare
CMIP7 replaces the MIP table with a realm, so `rewrite_mip_for_cmip7` rewrites `mip: Amon` to `mip: atmos` on each variable. Reference datasets are still CMOR-ised the CMIP6 way and are checked against a table, so the pass already pinned the original table onto a variable's own reference datasets. It did not reach references declared against the diagnostic as a whole, which inherited the realm instead. obs4MIPs names no table `atmos`, so the CMOR check failed with an empty frequency. Hoists the pinning so it covers both levels. A diagnostic-level reference applies to every variable, so it is only pinned when the variables agree on one table. This is what broke the cloud radiative effects CMIP7 mint. It also pins `AERmon` onto the two ozone diagnostic-level references, matching what ozone's own variable-level references already carry.
Description
Test the recipe from ESMValGroup/ESMValTool#4461
Checklist
Please confirm that this pull request has done the following:
changelog/