I propose a functionality within the cosima-cookbook which would be something like:
grid = cc.get_unmasked_grid(experiment)
The function, cc.get_unmasked_grid would have the path the grid is hardcoded in and could be updated when that path changes. This way the weight of knowing where the grids are is taken off from the shoulders of the users and goes to the shoulders of the cookbook developers.
At the moment to use the unmasked grids we need to know where they are saved and then do something like
(see, e.g., https://cosima-recipes.readthedocs.io/en/latest/tutorials/Making_Maps_with_Cartopy.html#fixing-the-tripole)
I propose a functionality within the
cosima-cookbook
which would be something like:The function,
cc.get_unmasked_grid
would have the path the grid is hardcoded in and could be updated when that path changes. This way the weight of knowing where the grids are is taken off from the shoulders of the users and goes to the shoulders of thecookbook
developers.cc: @AndyHoggANU, @aidanheerdegen, @angus-g, @micaeljtoliveira, @aekiss