-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Published recipes use deprecated fx_variables
option in preprocessors
#3056
Comments
@ESMValGroup/esmvaltool-coreteam Feel free to update this list if you encounter more recipes that need updates. |
The dataset name and version number needs to be updated for recipes using obs4MIPs datasets: #2974 |
the issue with collins and |
Yeah, I will remove them again from the list and only add recipes where we confirmed that they stopped working. I thought we can trust that automated test 🥲 |
the test can be trusted (if you talking about the GA test) - the reasons it fails are all upon us 😆 Do you want to try and run those collins et al recipes - like actual runs, as you suggested, Manu? Using a Core-dev env just like the test, but where data is available, if they pass it means it's some mocking issue like we've had before, if they fail then it's some Bouweing issue like we've had before 👿 |
We will test the recipes soon anyway, so I'll wait until that (don't want to waste resources on these huge recipes 😄 ) |
such an Ursula von der Leyen-like answer 🥇 |
Indeed, this is probably our most resource-intensive recipe and only runs on 512GB nodes at DKRZ... See https://esmvaltool.dkrz.de/shared/esmvaltool/v2.7.0/debug.html |
fx_variables
option in preprocessors
Partly addressed by #3064 |
well Collins13 is fixed now - I mean, it's still a memory guzzler, but at least Manu and Remi ran it - any more of those recipes need fixing? |
All the recipes not yet updated will continue to run fine with v2.8. |
Thanks to everyone who contributed to this effort already! I bumped this issue to the next milestone because we need to move on with the final recipe testing in v2.8 release. The remaining few recipes would need to be updated before the v2.9 release. |
Friendly ping @katjaweigel and @debe-kevin. Could you have a look at the recipes that you are maintaining and remove all mentions of |
@bouweandela thanks for the ping! I didn't notice it before, but I'm working on it now. |
Unfortunately I get an error (for ipccwg1ar5ch9/recipe_weigel21gmd_figures_13_16.yml and similar also for Error message (ipccwg1ar5ch9/recipe_flato13ipcc_figures_938_941_cmip6.ym):
|
Hm, seems there were some half finished things in there, yesterday. Getting the newest version now, it works again. |
Yes, there was a mistake ESMValGroup/ESMValCore#2085 in the code that has now been fixed. |
Sorry, that I don't manage to finish the PR today, some tests will run to long so I continue on Monday. |
This issue can now be closed since we do not have recipes in |
Due to recent changes in ESMValCore (ESMValGroup/ESMValCore#1609 and co.) we need to adapt some recipes because the usage of the option
fx_variables
in preprocessors is deprecated.These can be fixed by replacing
fx_variables
withsupplementary_variables
as described here.fx_variables
in recipe_mpqb_xch4 and recipe_lauer22jclim_fig8 #3117)recipe_impact.yml
write a CSV file that can directly be used in C4I portal #2258)fx_variables
in recipe_mpqb_xch4 and recipe_lauer22jclim_fig8 #3117)The text was updated successfully, but these errors were encountered: