It could be convenient if users could define their own preprocessor functions and use those from the recipe instead of being limited by what is available in ESMValCore. For example:
preprocessors:
# See https://docs.esmvaltool.org/projects/esmvalcore/en/latest/recipe/preprocessor.html
# for a description of the preprocessor functions.
annual_mean_amsterdam:
extract_location:
location: Amsterdam
scheme: linear
annual_statistics:
operator: mean
esmvaltool.diag_scripts.example.some_function:
example_argument: 10
multi_model_statistics:
statistics:
- mean
span: overlap
convert_units:
units: degrees_C
where esmvaltool.diag_scripts.example.some_function is a Python function in the module esmvaltool.diag_scripts.example with the function signature
def some_function(cube: iris.cube.Cube, example_argument: int) -> iris.cube.Cube:
This would make using the preprocessing capabilities of the recipe more powerful because recipe authors can include their own Python functions that may not need to be of general interest.
@ESMValGroup/technical-lead-development-team Opinions anyone?
It could be convenient if users could define their own preprocessor functions and use those from the recipe instead of being limited by what is available in ESMValCore. For example:
where
esmvaltool.diag_scripts.example.some_functionis a Python function in the moduleesmvaltool.diag_scripts.examplewith the function signatureThis would make using the preprocessing capabilities of the recipe more powerful because recipe authors can include their own Python functions that may not need to be of general interest.
@ESMValGroup/technical-lead-development-team Opinions anyone?