-
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
Remove recipe filler utility #3777
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, Manu, been tied up all day today fixing all manners of technical gubbins in ESMValTool. Let me have a closer look at this tomorrow - have you asked around about this, I know there are quite a few folks that still use the recipe filler eg @ledm @egalytska etc - note that the wildcard approach is not exactly equivalent with the recipe filler: that will find and run everything that is available, whereas the recipe filler will tell the user what is available before the actual run, then the user will decide what data to run with
Don't worry, I would never merge this without proper discussion! Sorry, opening this PR takes as much time as opening an issue, so I thought I might as well do that! Regarding the features:
This can also be achieved with the wildcard syntax. For every ESMValTool run, a filled recipe is written which, in case wildcards are used, contains all expanded datasets. User can modify this as they wish to achieve the same functionality as the recipe filler. Also, the wildcard syntax fixes some of the limitations of the recipe filler:
|
Oh that's very nice about the filled recipe! Didn't know about that feature - that's that sold to me, in this case, but let's still ask some of the users, not being a user per se myself, am not aware of potential used cases users may be employing the recipe filler for. Thanks, Manu 🍺 |
That all sounds good to me. |
@egalytska indeed we'll mention that as you say, in the 2.12 release notes, and the recipe filler still lives in history ie in 2.11 and before 🍺 |
@ESMValGroup/esmvaltool-developmentteam In this pull request we plan to remove the recipe filler utility because it has become obsolete (see details on the pull request description above). If you are a regular user of this tool and/or think we should not remove it, please let us know as soon as possible by commenting here. Thanks!! |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
It looks like no one disagrees with this, so I guess we can safely go ahead with this PR! @valeriupredoi if you agree, would you please merge this? Thanks! 🍻 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RIP, Recipe Filler, you was a gud boi 😭 Cheers, Manu 🍺
devel tests are with iris=3.11 and those fails are fixed by #3810 |
* main: (31 commits) Update environment: pin `iris>=3.11`, unpin `cartopy` and allow for `numpy >=2` (#3811) Fix issue related to removal/change of private function imported in `diag_scripts/shared/_supermeans.py` (deprecation in iris=3.11) (#3810) Remove recipe filler utility (#3777) [Condalock] Update Linux condalock file (#3809) change authors name (#3806) [Condalock] Update Linux condalock file (#3798) Fix contourf plots for masked data (#3797) [Condalock] Update Linux condalock file (#3796) Add next release schedule (#3794) Use `transform_first=True` for contourf plots with Robinson projection to avoid cartopy bug (#3789) Pin pys2index >=0.1.5 in osx environment (#3792) Adding a CMORiser for CMAP data for pr (#3766) Adding pr, tauu, tauv, tos to NCEP2 CMORISer (#3765) Readthedocs configuration/builds: revert to miniconda before miniforge is available (#3785) Adapt ESMValTool to new configuration (#3761) Adding pr, tauu, tauv NOAA-CIRES-20CR-V2 CMORISER (#3763) update comment in conda lock creation Github action (#3788) [Condalock] Update Linux condalock file (#3786) update Docker builds badge in README (#3783) Pin mamba<2 for conda-lock: solution by Ben Mares @maresb (#3771) ...
…Tool into 3723_remove_rose_cylc * '3723_remove_rose_cylc' of github.com:ESMValGroup/ESMValTool: (31 commits) Update environment: pin `iris>=3.11`, unpin `cartopy` and allow for `numpy >=2` (#3811) Fix issue related to removal/change of private function imported in `diag_scripts/shared/_supermeans.py` (deprecation in iris=3.11) (#3810) Remove recipe filler utility (#3777) [Condalock] Update Linux condalock file (#3809) change authors name (#3806) [Condalock] Update Linux condalock file (#3798) Fix contourf plots for masked data (#3797) [Condalock] Update Linux condalock file (#3796) Add next release schedule (#3794) Use `transform_first=True` for contourf plots with Robinson projection to avoid cartopy bug (#3789) Pin pys2index >=0.1.5 in osx environment (#3792) Adding a CMORiser for CMAP data for pr (#3766) Adding pr, tauu, tauv, tos to NCEP2 CMORISer (#3765) Readthedocs configuration/builds: revert to miniconda before miniforge is available (#3785) Adapt ESMValTool to new configuration (#3761) Adding pr, tauu, tauv NOAA-CIRES-20CR-V2 CMORISER (#3763) update comment in conda lock creation Github action (#3788) [Condalock] Update Linux condalock file (#3786) update Docker builds badge in README (#3783) Pin mamba<2 for conda-lock: solution by Ben Mares @maresb (#3771) ...
Description
With the introduction of the wildcard syntax for recipes in ESMValGroup/ESMValCore#1609 the recipe filler utility has become obsolete. After parsing a recipe, ESMValTool will automatically create a "filled" version of the recipe (available in the
run
output directory) with all wildcards expanded, which can then be modified by the user and run again.Details on how to use the new wildcard syntax: https://docs.esmvaltool.org/projects/ESMValCore/en/latest/recipe/overview.html#automatically-populating-a-recipe-with-all-available-datasets
Example notebook: https://github.com/ESMValGroup/ESMValCore/blob/main/notebooks/discovering-data.ipynb
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.
To help with the number of pull requests: