-
Notifications
You must be signed in to change notification settings - Fork 128
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
Recipe testing and comparison for release 2.11.0 #3616
Comments
Thanks for the check! |
Sorry, somehow I hit the wrong button when I tried to remove a comment. Unfortunately, the issue with recipe_martin18grl.yml is more complicated than I thought before. The reason that it cannot write the figure/provenance is, that the name of some models is not found correctly anymore in droughtindex/collect_drought_*.py. The way these python diagnostics identified the models was never really good: Since the data are previously modified by the R script (diag_save_spi.R) and forwarded through ancestors in the recipe, the information about the model name was not in the cfg automatically, so I used the information in cube [model_id or source_id in cube.metadata.attributes after iris.load]. (This was never a really good idea, because due to the different keys in the attributes, it only worked for CMIP5 and CMIP6 models). Unfortunately, now this information is not there anymore for some CMIP5 models (e.g. GISS-E2-H # ) for others it still works. The reason could be somewhere in the R script, or even already in the preprocessor? (And I'm not sure if it would not be better to improve the way the python script gets its information instead of fixing it in R). # |
@lukruh I think you had a better method to forward information when using ancestors? |
I usually let the ancestors create a metadata.yml in the work folder similar to the one the preprocessor creates in the preproc folders. I can have a look on the Code later. |
It looks like it comes already out of the preprocessor: |
But it only gets a problem through R: I read the preproc data, which have the attributes in the variable with R. Afterwards the variable attributes are gone, so the python diagnostic cannot pick them up anymore. |
Below is a summary of the comparison results (full comparison details are available in compare_v2.10.0_v2.11.0rc1_output.txt). @ESMValGroup/esmvaltool-recipe-maintainers and @ESMValGroup/esmvaltool-coreteam we would be very grateful if you would check the recipe outputs are still correct. Tick the box and add your name next to the recipe once you've checked. Runs with v2.11.0rc1: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.11.0rc1/ The recipes where plots are different are probably the most important to check because if the data are different but the plots still look the same the changes are probably not significant. Maybe we can refine the thresholds for when data is reported as different for a future version of the comparison tool. Plots and data are different (39 recipes)
Only plots are different (9 recipes)
Only data are different (38 recipes)
Results are the same as v2.10.0 (38 recipes)Click to expand
Unable to compare because no reference run for v2.10.0 (8 recipes)
Known broken recipes (1 recipe)
|
Thanks to those who have checked recipes so far! Please keep checking, we are aiming to finalise the release process on Thursday this week 🙂 |
Apologies for the late answer, I was on vacation.
Pre-v2.11.0: v2.11.0: I have not idea what's causing this. Try to have a look at this tomorrow.
|
|
Thank you for checking @schlunma! 🎉 ESMValGroup/ESMValCore#2421 (comment) suggests that this recipe ran successfully, so I believe it should instead be in the |
Closing this issue now the release has been completed 👍 |
Test results
See https://esmvaltool.dkrz.de/shared/esmvaltool/v2.11.0rc1/.
Comparisons
Action required: 95 out of 133 recipe runs need to be inspected by a human.
See comparison_output_v2.11.0rc1.txt.
Path to the output directories on DKRZ/Levante:
/scratch/b/b382148/esmvaltool_output
System and settings
environment_v2.11.0.txt
This is what @ehogan did on DKRZ: ESMValGroup/ESMValCore#2389 (reply in thread)
Recipe running session 2024-05-24 10:41:05.726830
Recipes that ran successfully (136 out of 160)
Click to expand
Recipes that failed because the diagnostic script failed (7 out of 160)
Recipes that failed because of missing data (3 out of 160)
Recipes that failed because the run took too long (4 out of 160)
Recipes that failed because they used too much memory (2 out of 160)
Recipes that failed of other reasons or are still running (8 out of 160)
Analysis of failures are detailed here ESMValGroup/ESMValCore#2421 (comment)
The text was updated successfully, but these errors were encountered: