As more recipes are added to ESMValTool we might need a way to structure them by project. For example, for the eWaterCycle project we will use ESMValTool to do pre-processing for hydrology models. I propose adding a layer of folders in the esmvaltool/recipes folder that clusters recipes of certain projects together. e.g. esmvaltool/recipes/eWaterCycle.
I think this will increase usability. The ESMValTool documentation would also benefit from such a structure.
Maybe structuring by project is not the best way. Another option is structuring by use, e.g esmvaltool/recipes/hydrology and esmvaltool/recipes/climate?
As more recipes are added to ESMValTool we might need a way to structure them by project. For example, for the eWaterCycle project we will use ESMValTool to do pre-processing for hydrology models. I propose adding a layer of folders in the
esmvaltool/recipes
folder that clusters recipes of certain projects together. e.g.esmvaltool/recipes/eWaterCycle
. I think this will increase usability. The ESMValTool documentation would also benefit from such a structure.