Recipe running results for v2.6.0rc3 and v2.6.0rc4 #2704
Comments
|
Great, thanks for the overview! Could you briefly post the paths on Levante from the rc2 and rc3 results so I can run the tool to compare the outputs myself (to get more detailed output). Thanks! |
|
Hi, results for |
|
@schlunma I am afraid results from rc2 are no longer available in levante because they were in my scratch, just in https://esmvaltool.dkrz.de/shared/esmvaltool/v2.6.0rc2 For rc3, the results are here: |
|
Ah, so you compared the runs to v2.5.0? Could you point me to the location where this is stored on Levante? |
|
Yes, but I ran the comparison in the esmvaltool machine, using the 2.5.0 outputs that are there. I installed the tool in my home and pointed to the results in /shared |
|
For |
@schlunma you can find a copy of the final output for v2.5 recipes in |
|
Thanks @remi-kazeroni 👍 |
|
Yesterday I started comparing the different runs for some of the recipe (I will continue tomorrow since Levante is on maintenance today). I noticed two things so far:
|
This sounds easiest, maybe just sort the datasets alphabetically? |
|
Although marked as unchanged, some peculiar additional frames around maps appeared in recipe_li17natcc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_li17natcc_20220701_071843 as well as in |
Yes, I think so, too. I already started implementing this, will continue tomorrow. |
|
@schlunma, @bouweandela, wrt sorting, as far as I can see the |
|
Ah, so the sorting done before saving the file is not sufficient? |
|
No, because there with and add the corresponding at the top which will clue in the reader on the other side to heed the order. |
|
I though regular see e.g., here:
|
|
You are right, that escaped me. However, the yaml data model doesn't take that into account, see yaml spec Section 1.2.2. Of course, that might still be unrelated 🤷, but if we think the order should be reflected in the yaml file, we could use an ordered dict. |
|
Thank you all for taking a look, I will wait until Friday for the remaining recipes. If by then they are not taken care of, I will take a quick look. But bear in mind that I am not going to look in depth, so some issues may go unnoticed. |
This seems not directly related to the change from v2.5 to v2.6 (maybe it is intreduced by a new version of matplotlib?). However, I opened an Issue here: #2711 |
|
@ESMValGroup/esmvaltool-developmentteam please find below a summary of the changes for the remaining recipes. I will split it in several comments becaue the summary is rather large. Summary of remaining recipes
Complains of differing netcdf files, however there seems to be no issue with any on the png files that get generated. So I am going to assume that the differences are coming from some sort of attribute and that they are not a big deal:
Complains about the following csv differing files: Checked and the numerical results are not quite identical due to precision, for instance:
No comparison, because the diagnostic fails in v2.5.0 . I guess because this is one of the metrics that needs to run in jasmin.
Complains about cvs files, same issue as in recipe_autoassess_landsurf_permafrost
Complains about cvs files, same issue as in recipe_autoassess_landsurf_permafrost
No differences in plots nor work files, just complains about the presence of extra files that I guess were deleted from the 2.5 outputs.
Complains about some differing netcdf files, but no issues with any of the plots files. There are complaints both about the data being different and some attributes. I can't comment on the data being different.
Complains about differing results in both netcdf and a plot about Can't really comment on these.
Complains about differing plots/capacity_factor/main/capacity_factor_CMCC-CMS_1980-2005.png plot, checked and it seems like the size of the plot is different but the results are identical.
Complains about differing netcdf files, but no issues with any of the plots files. Differences are mostly due to differing attributes but there is one file where data is different:
However, it's the only climwip recipe that gives issues, and it happens to be the test one not the "real" ones. So I am going to assume whatever is the issue, is not a big deal.
Complains about differing netcdf files, but no issues with any of the plots files. I am going to assume the difference are due to attributes, rather than issues with the data.
Complains about differing netcdf files, but no issues with any of the plots files. I am going to assume the difference are due to attributes, rather than issues with the data.
Complains because the run for rc3 did not finish because of the job submission. But the output comparison for rc2 with respect to 2.5 gives identical results
Complains about plots/combine_indices/main/Nino3.4_tos_Dec-Feb_running-mean__1950-2005.png but the results look identical to me
Complains about a plot, probably related to #2671
Complains about netcdf files and some namelists. However, whatever may be the issue it can't be related to the core because cvdp is an external package.
Complains about extra files present between runs that were probably deleted form the 2.5 outputs.
Complains about a plot but it looks identical to me
Complains about extra files present between runs that were probably deleted form the 2.5 outputs.
Complains about plots, but they look identical to me. This is happening in all magic recipes developed by the BSC.
Complains about extra files present between runs that were probably deleted form the 2.5 outputs.
Another magic recipe that complains about the plots but that, to my inexpert eye, look the same.
Complains about differing netcdf files, but no issues with any of the plots files. I am going to assume the difference are due to attributes, rather than issues with the data.
I cannot really comment on that. I doubt it's an issue of the core because the only thing the preproc does is using mask_landsea |
Complains about differing plots and netcdf. I doubt it's an issue of the core because the only thing the preproc does is using mask_landsea
Can't really comment on that
Complains about differing netcdf and plots. Differing files: Can't comment on that. I doubt it's an issue with the core because the only thing the preproc does is using regrid.
Complains about differing netcdf files, but no issues with any of the plots files. I am going to assume the difference are due to attributes, rather than issues with the data.
Complains about differing netcdf files, but no issues with any of the plots files. I am going to assume the difference are due to attributes, rather than issues with the data.
Complains about differing mat files, but no issues with any of the plots files. I am going to assume the difference are due to attributes, rather than issues with the data.
Complains about the presence of extra files between runs that probably were deleted from th 2.5.0 outputs
Another magic recipe that reports differences in plots but results look identical
Differences in the following plots: I cannot comment on that
Another magic recipe complaining about differing results even though the plots look the same to me.
Complains about a missing file that then reappears as an extra file with a different name:
Differences on some plots due to the recently updated
Differing netcdf and epsi files. However there are not complaints about differing plots, so it's probably an issue with metadata.
Differing plots that I cannot comment on:
Differing plot and netcdf for a certain dataset that I cannot comment on:
Complains about differing netcdf files but no issues in plots so I am going to assume that they are due to some attributes
Complains about differing netcdf files but no issues in plots so I am going to assume that they are due to some attributes
Complains about differing netcdf files but no issues in plots so I am going to assume that they are due to some attributes
Complains about differing xlsx files. I guess it's the same issue about differences being reported in cvs files
Complains about the presence of extra files between runs that were probably deleted from the v2.5 runs |
Complains about differing netcdf files but no issues in plots so I am going to assume that they are due to some attributes
Differences in netcdf and plots: Can't really comment on that
Complains about differing netcdf files but no issues in plots so I am going to assume that they are due to some attributes
Complains about differing netcdf files but no issues in plots so I am going to assume that they are due to some attributes
Complains about differing netcdf, pdf and epsi files but no issues in plots so I am going to assume that they are due to some attributes |
|
So as an overall conclusion, there are less than 10 recipes that truly seem to have an issue going on with the numerical results of the run. However, I think it would be very obvious if it was something in the core breaking because it would be affecting many recipes (especially the preprocessor testing ones). @ESMValGroup/esmvaltool-coreteam I would say the core is ready to be officially released, but if any of you strongly oposes let me know. |
|
@sloosvel, don't forget to check the tests. You might want to pickup ESMValGroup/ESMValCore#1656. |
|
@sloosvel There has been a lot of discussion about backward incompatible changes and deprecating stuff recently. One of the main conclusions from that is that we need to clearly list deprecated and removed features in the changelog and provide a detailed upgrade guide in the same place. I see that there is one deprecated feature (and no removed features, is that correct?) listed in the changelog, but right now it is somewhere near the bottom of the list of changes and it misses instructions on how to upgrade. I think it is important that this is addressed before the release. @schlunma Since you contributed the deprecated feature, could you please take care of adding an upgrade guide for this to the changelog and move it so it is listed right under the highlights section? |
|
Ok I will open an issue in the core. But this release is already very overdue. |
|
That must have been a lot of work, reviewing all those recipe runs @sloosvel, thanks for taking care!
If you run the comparison with the
It should support .csv files (see here) and if it does not than that would be a bug in the comparison tool. To see which lines are different, you can run it with the
It might be good to check this in a bit more detail: a timerange appeared in the name of a file that is time independent and you did quite a bit of work on timeranges for this release, so I think this change could indicate a newly introduced bug in the ESMValCore.
If you run the compare tool with the |
|
Thanks that should be helpful, I was not aware of the |
|
|
Running with verbose shows a lot of netcdf files where the data is different but I don't understand why this does not affect the plots in most cases. I don't think I can trace back every single source of difference. |
The work on the timeranges was mostly for the past release though. I will double check anyway. |
Not on the plots though |
That is exactly why we need help from the @ESMValGroup/esmvaltool-developmentteam with making a release. Please give @sloosvel a hand with this release everyone. She has provided us with a great overview of recipes that potentially have issues. The results from the current run are available here and from the previous version here. We have a small tool available to drill down into what has changed, the documentation is available here (don't forget to use the |
@sloosvel Do you have ideas for how this could be implemented? |
As of right now, no. But again taking a look is quite clear in this case that the differences are not huge. We already discussed the source of differences in ESMValGroup/ESMValCore#1545. |
I know but at some point there has to be a compromise, and it's clear that a lot of people that contributed in the past are no longer active. I will run more comparisons between versions and also check if maybe the precision that is expected for the comparison for the netcdfs is too high to have a big impact on the plots. And if after that the missing recipes have not been claimed I think they will have to go into the release as they are, since they have probably been unmaintained for quite some time. |
|
so here's a good point @sloosvel is raising - I'd add a level of maintenance per recipe: colour-coded: green - well maintained, yellow so-so, red - abandonware, so people know what to expect when running them. Also, if plots look the same, then I wouldn't worry too much. Cheers for all the heavy-lifting, Saskia! 🍺 |
|
An example I found where the netcdf files differed and plots didn't were netcdf files that inlcude a |
|
I would also take into account that v2.5 was ran in a different machine than v2.6 |
are we actually seeing machine precision deltas? Would think those would be swamped by numerical library differences 🖥️ 🐍 |
|
@sloosvel thanks for all the tests! I'll have a look at recipe_pv_capacity_factor now, I overlooked that in the first list. |
|
The plots from recipe_pv_capacity_factor are ok, the change seems to be the font of the plot titles (new R version, maybe), looks similar for recipe_capacity_factor.yml. |
|
Thanks for checking @katjaweigel !! I think many R recipes (the magic ones at least) have a similar issue in which results look similar but the tool says otherwise, so it must be due to small differences like fontsize and such. I also took the time to do some comparisons using the outputs from 2.4.0 compared to 2.5.0, and for the following recipes, the tool reports the same differences in netcdf files as the comparison of 2.5.0 with 2.6.0:
So I am going to tick these ones out, as well because if the differences in the netcdf persist across releases but the plots seem to be fine, it can't be due to breaking changes. |
sloosvel
changed the title
|
You can find the results for release candidate 4 of ESMValCore here: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.6.0rc4/ Nothing seems to have changed with respect rc3, the comparison with 2.5.0 gives the same results. If there are no further comments, I will be doing the final release of ESMValCore tomorrow. |
|
Thanks for all your work on the release @sloosvel including running all the recipes and comparing the output! For the sake of completeness, you could run the comparison tool between rc3 and rc4 outputs directly to check that nothing has changed. But if you have not witnessed any changes when comparing to v2.5.0 results, I think you can proceed with the final release 👍 Do I understand correctly that the release of the Core will be soon followed by the one of the Tool? In that case, shall we close milestone v.2.6.0 and transfer open issues/PRs to milestone v2.7.0? |
Yes of course, here are the results. As you can see it's the same recipes that keep reporting the same issues. So I really think that for these selected recipes, the comparison tool is probably picking up differences that keep changing between runs regardless if they have a big impact on the results or not. Also the
Ideally I would like to release the tool next week. I think it's fair to give time to include some corrections that @katjaweigel detected for her recipes (#2711) and then I need to update some documentation myself. For issues were more work is required, I am afraid some of them will have to be moved to the next milestone but I will check each one of them individually. |
|
@sloosvel sorry for the last minute check on |
|
Thank you all, version 2.6 is now available. Hopefully this first run of the comparison tool will help subsequent releases. |
@ESMValGroup/esmvaltool-developmentteam @ESMValGroup/esmvaltool-recipe-maintainers please, feel free to check the recipe running results using ESMValCore v2.6.0rc3 in the following link: https://esmvaltool.dkrz.de/shared/esmvaltool/v2.6.0rc3/
There have not been any changes with respect v2.6.0rc2 in terms of failures when running the recipes.
However the recipe comparison tool developed by @bouweandela reports that 79 recipes need to be inspected by a human due to differences in the results with respect to v2.5.0:
Summary
recipe_albedolandcover.yml: /shared/esmvaltool/v2.6.0rc3/recipe_albedolandcover_20220701_070913
recipe_climwip_brunner2019_med.yml: /shared/esmvaltool/v2.6.0rc3/recipe_climwip_brunner2019_med_20220701_070951
recipe_climwip_brunner20esd.yml: /shared/esmvaltool/v2.6.0rc3/recipe_climwip_brunner20esd_20220701_074428
recipe_climwip_test_basic.yml: /shared/esmvaltool/v2.6.0rc3/recipe_climwip_test_basic_20220701_074404
recipe_concatenate_exps.yml: /shared/esmvaltool/v2.6.0rc3/recipe_concatenate_exps_20220701_080134
recipe_correlation.yml: /shared/esmvaltool/v2.6.0rc3/recipe_correlation_20220701_080151
recipe_deangelis15nat.yml: /shared/esmvaltool/v2.6.0rc3/recipe_deangelis15nat_20220701_073236
recipe_decadal.yml: /shared/esmvaltool/v2.6.0rc3/recipe_decadal_20220701_080248
recipe_eady_growth_rate.yml: /shared/esmvaltool/v2.6.0rc3/recipe_eady_growth_rate_20220701_071105
recipe_ecs_scatter.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ecs_scatter_20220701_072257
recipe_esacci_lst.yml: /shared/esmvaltool/v2.6.0rc3/recipe_esacci_lst_20220701_071326
recipe_esacci_oc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_esacci_oc_20220701_073012
recipe_extract_shape.yml: /shared/esmvaltool/v2.6.0rc3/recipe_extract_shape_20220701_080152
recipe_eyring06jgr.yml: /shared/esmvaltool/v2.6.0rc3/recipe_eyring06jgr_20220701_071318
recipe_eyring13jgr_12.yml: /shared/esmvaltool/v2.6.0rc3/recipe_eyring13jgr_12_20220701_071013
recipe_hype.yml: /shared/esmvaltool/v2.6.0rc3/recipe_hype_20220701_075500
recipe_julia.yml: /shared/esmvaltool/v2.6.0rc3/recipe_julia_20220701_080222
recipe_li17natcc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_li17natcc_20220701_071843
recipe_my_personal_diagnostic.yml: /shared/esmvaltool/v2.6.0rc3/recipe_my_personal_diagnostic_20220701_080034
recipe_ocean_amoc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_amoc_20220701_071014
recipe_ocean_ice_extent.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_ice_extent_20220701_073956
recipe_ocean_quadmap.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_quadmap_20220701_070916
recipe_ocean_scalar_fields.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_scalar_fields_20220701_070912
recipe_pcrglobwb.yml: /shared/esmvaltool/v2.6.0rc3/recipe_pcrglobwb_20220701_075619
recipe_preprocessor_derive_test.yml: /shared/esmvaltool/v2.6.0rc3/recipe_preprocessor_derive_test_20220701_080318
recipe_preprocessor_test.yml: /shared/esmvaltool/v2.6.0rc3/recipe_preprocessor_test_20220701_080215
recipe_python.yml: /shared/esmvaltool/v2.6.0rc3/recipe_python_20220701_080304
recipe_r.yml: /shared/esmvaltool/v2.6.0rc3/recipe_r_20220701_080104
recipe_radiation_budget.yml: /shared/esmvaltool/v2.6.0rc3/recipe_radiation_budget_20220701_072419
recipe_seaice_drift.yml: /shared/esmvaltool/v2.6.0rc3/recipe_seaice_drift_20220701_074322
recipe_seaice_feedback.yml: /shared/esmvaltool/v2.6.0rc3/recipe_seaice_feedback_20220701_072347
recipe_snowalbedo.yml: /shared/esmvaltool/v2.6.0rc3/recipe_snowalbedo_20220701_073825
recipe_validation_CMIP6.yml: /shared/esmvaltool/v2.6.0rc3/recipe_validation_CMIP6_20220701_070916
recipe_variable_groups.yml: /shared/esmvaltool/v2.6.0rc3/recipe_variable_groups_20220701_080222
recipe_williams09climdyn_CREM.yml: /shared/esmvaltool/v2.6.0rc3/recipe_williams09climdyn_CREM_20220701_070943
The following recipe runs need to be inspected by a human:
recipe_anav13jclim.yml: /shared/esmvaltool/v2.6.0rc3/recipe_anav13jclim_20220701_072853
recipe_arctic_ocean.yml: /shared/esmvaltool/v2.6.0rc3/recipe_arctic_ocean_20220701_070916
recipe_autoassess_landsurface_permafrost.yml: /shared/esmvaltool/v2.6.0rc3/recipe_autoassess_landsurface_permafrost_20220701_075243 --> Differences in the last decimals for the values in cvs files.
recipe_autoassess_landsurface_soilmoisture.yml: /shared/esmvaltool/v2.6.0rc3/recipe_autoassess_landsurface_soilmoisture_20220704_125522 --> Differences in the last decimals for the values in cvs files.
recipe_autoassess_radiation_rms_Amon_all.yml: /shared/esmvaltool/v2.6.0rc3/recipe_autoassess_radiation_rms_Amon_all_20220701_070913 --> Differences in the last decimals for the values in cvs files.
recipe_autoassess_radiation_rms_Amon_obs.yml: /shared/esmvaltool/v2.6.0rc3/recipe_autoassess_radiation_rms_Amon_obs_20220701_073354 --> Differences in the last decimals for the values in cvs files.
recipe_autoassess_stratosphere.yml: /shared/esmvaltool/v2.6.0rc3/recipe_autoassess_stratosphere_20220701_075100
recipe_bock20jgr_fig_1-4.yml: /shared/esmvaltool/v2.6.0rc3/recipe_bock20jgr_fig_1-4_20220704_073821
recipe_bock20jgr_fig_6-7.yml: /shared/esmvaltool/v2.6.0rc3/recipe_bock20jgr_fig_6-7_20220704_073839
recipe_bock20jgr_fig_8-10.yml: /shared/esmvaltool/v2.6.0rc3/recipe_bock20jgr_fig_8-10_20220701_080535
recipe_capacity_factor.yml: /shared/esmvaltool/v2.6.0rc3/recipe_capacity_factor_20220701_070917
recipe_carvalhais14nat.yml: /shared/esmvaltool/v2.6.0rc3/recipe_carvalhais14nat_20220701_071703
recipe_climate_change_hotspot.yml: /shared/esmvaltool/v2.6.0rc3/recipe_climate_change_hotspot_20220704_092901 --> New recipe
recipe_climwip_test_performance_sigma.yml: /shared/esmvaltool/v2.6.0rc3/recipe_climwip_test_performance_sigma_20220701_073258
recipe_clouds_bias.yml: /shared/esmvaltool/v2.6.0rc3/recipe_clouds_bias_20220701_070916
recipe_clouds_ipcc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_clouds_ipcc_20220701_070913
recipe_cmug_h2o.yml: /shared/esmvaltool/v2.6.0rc3/recipe_cmug_h2o_20220701_070913
recipe_collins13ipcc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_collins13ipcc_20220704_074213
recipe_combined_indices.yml: /shared/esmvaltool/v2.6.0rc3/recipe_combined_indices_20220701_070913
recipe_consecdrydays.yml: /shared/esmvaltool/v2.6.0rc3/recipe_consecdrydays_20220701_071629
recipe_cox18nature.yml: /shared/esmvaltool/v2.6.0rc3/recipe_cox18nature_20220701_071615
recipe_cvdp.yml: /shared/esmvaltool/v2.6.0rc3/recipe_cvdp_20220701_075314
recipe_daily_era5.yml: /shared/esmvaltool/v2.6.0rc3/recipe_daily_era5_20220701_075330
recipe_deangelis15nat_fig1_fast.yml: /shared/esmvaltool/v2.6.0rc3/recipe_deangelis15nat_fig1_fast_20220701_080356
recipe_diurnal_temperature_index.yml: /shared/esmvaltool/v2.6.0rc3/recipe_diurnal_temperature_index_20220701_071214
recipe_ecs.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ecs_20220701_071515
recipe_ecs_constraints.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ecs_constraints_20220701_070912
recipe_era5-land.yml: /shared/esmvaltool/v2.6.0rc3/recipe_era5-land_20220701_074558
recipe_extreme_index.yml: /shared/esmvaltool/v2.6.0rc3/recipe_extreme_index_20220701_071515
recipe_gier2020bg.yml: /shared/esmvaltool/v2.6.0rc3/recipe_gier2020bg_20220701_073323
recipe_globwat.yml: /shared/esmvaltool/v2.6.0rc3/recipe_globwat_20220701_075500
recipe_heatwaves_coldwaves.yml: /shared/esmvaltool/v2.6.0rc3/recipe_heatwaves_coldwaves_20220701_072653
recipe_hydro_forcing.yml: /shared/esmvaltool/v2.6.0rc3/recipe_hydro_forcing_20220701_075939
recipe_hyint.yml: /shared/esmvaltool/v2.6.0rc3/recipe_hyint_20220701_071630
recipe_hyint_extreme_events.yml: /shared/esmvaltool/v2.6.0rc3/recipe_hyint_extreme_events_20220701_072023
recipe_kcs.yml: /shared/esmvaltool/v2.6.0rc3/recipe_kcs_20220701_070913
recipe_landcover.yml: /shared/esmvaltool/v2.6.0rc3/recipe_landcover_20220701_073120
recipe_lauer13jclim.yml: /shared/esmvaltool/v2.6.0rc3/recipe_lauer13jclim_20220701_071544
recipe_lisflood.yml: /shared/esmvaltool/v2.6.0rc3/recipe_lisflood_20220701_075651
recipe_marrmot.yml: /shared/esmvaltool/v2.6.0rc3/recipe_marrmot_20220701_075735
recipe_martin18grl.yml: /shared/esmvaltool/v2.6.0rc3/recipe_martin18grl_20220701_071025
recipe_meehl20sciadv.yml: /shared/esmvaltool/v2.6.0rc3/recipe_meehl20sciadv_20220701_071214
recipe_modes_of_variability.yml: /shared/esmvaltool/v2.6.0rc3/recipe_modes_of_variability_20220701_073544
recipe_monitor.yml: /shared/esmvaltool/v2.6.0rc3/recipe_monitor_20220701_080705 --> differences are due to a change in the output format (from svg to png)
recipe_monitor_with_refs.yml: /shared/esmvaltool/v2.6.0rc3/recipe_monitor_with_refs_20220701_080535
recipe_mpqb_xch4.yml: /shared/esmvaltool/v2.6.0rc3/recipe_mpqb_xch4_20220701_080516
recipe_multimodel_products.yml: /shared/esmvaltool/v2.6.0rc3/recipe_multimodel_products_20220701_070913
recipe_ncl.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ncl_20220701_080215
recipe_ocean_Landschuetzer2016.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_Landschuetzer2016_20220701_074530
recipe_ocean_bgc.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_bgc_20220701_073636
recipe_ocean_example.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_example_20220701_071723
recipe_ocean_multimap.yml: /shared/esmvaltool/v2.6.0rc3/recipe_ocean_multimap_20220701_071013
recipe_perfmetrics_CMIP5.yml: /shared/esmvaltool/v2.6.0rc3/recipe_perfmetrics_CMIP5_20220701_072823
recipe_perfmetrics_CMIP5_4cds.yml: /shared/esmvaltool/v2.6.0rc3/recipe_perfmetrics_CMIP5_4cds_20220701_070912
recipe_psyplot.yml: /shared/esmvaltool/v2.6.0rc3/recipe_psyplot_20220701_073751
recipe_pv_capacity_factor.yml: /shared/esmvaltool/v2.6.0rc3/recipe_pv_capacity_factor_20220701_071014
recipe_quantilebias.yml: /shared/esmvaltool/v2.6.0rc3/recipe_quantilebias_20220701_073220
recipe_rainfarm.yml: /shared/esmvaltool/v2.6.0rc3/recipe_rainfarm_20220701_071431
recipe_runoff_et.yml: /shared/esmvaltool/v2.6.0rc3/recipe_runoff_et_20220701_070913
recipe_russell18jgr.yml: /shared/esmvaltool/v2.6.0rc3/recipe_russell18jgr_20220701_074628
recipe_schlund20esd.yml: /shared/esmvaltool/v2.6.0rc3/recipe_schlund20esd_20220630_110419
recipe_schlund20jgr_gpp_abs_rcp85.yml: /shared/esmvaltool/v2.6.0rc3/recipe_schlund20jgr_gpp_abs_rcp85_20220701_080126
recipe_schlund20jgr_gpp_change_1pct.yml: /shared/esmvaltool/v2.6.0rc3/recipe_schlund20jgr_gpp_change_1pct_20220701_080004
recipe_schlund20jgr_gpp_change_rcp85.yml: /shared/esmvaltool/v2.6.0rc3/recipe_schlund20jgr_gpp_change_rcp85_20220701_080034
recipe_sea_surface_salinity.yml: /shared/esmvaltool/v2.6.0rc3/recipe_sea_surface_salinity_20220701_074628 --> result changed but it's intentional (see Compute bias instead of correlation in
compare_salinity.py#2642 )recipe_seaice.yml: /shared/esmvaltool/v2.6.0rc3/recipe_seaice_20220701_074457
recipe_shapeselect.yml: /shared/esmvaltool/v2.6.0rc3/recipe_shapeselect_20220701_070912
recipe_smpi.yml: /shared/esmvaltool/v2.6.0rc3/recipe_smpi_20220704_074904
recipe_spei.yml: /shared/esmvaltool/v2.6.0rc3/recipe_spei_20220701_071544
recipe_tcr.yml: /shared/esmvaltool/v2.6.0rc3/recipe_tcr_20220701_071445
recipe_thermodyn_diagtool.yml: /shared/esmvaltool/v2.6.0rc3/recipe_thermodyn_diagtool_20220701_072114
recipe_toymodel.yml: /shared/esmvaltool/v2.6.0rc3/recipe_toymodel_20220701_072419
recipe_validation.yml: /shared/esmvaltool/v2.6.0rc3/recipe_validation_20220701_071925
recipe_wenzel16jclim.yml: /shared/esmvaltool/v2.6.0rc3/recipe_wenzel16jclim_20220701_072526
recipe_wenzel16nat.yml: /shared/esmvaltool/v2.6.0rc3/recipe_wenzel16nat_20220627_084252
recipe_wenzel16nat.yml: /shared/esmvaltool/v2.6.0rc3/recipe_wenzel16nat_20220630_131043
recipe_wenzel16nat.yml: /shared/esmvaltool/v2.6.0rc3/recipe_wenzel16nat_20220630_131144
recipe_wflow.yml: /shared/esmvaltool/v2.6.0rc3/recipe_wflow_20220701_075746
recipe_zmnam.yml: /shared/esmvaltool/v2.6.0rc3/recipe_zmnam_20220701_070930
So if you are a human and your recipe is needs to be inspected, please check the recipe box and report back if there are any major differences in the results.
The text was updated successfully, but these errors were encountered: