Sparse regridding without using ESMF #130
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR shows how one can avoid using xESMF for the application of the regridding weights, by using sparse matrix multiplication instead. The motivation for this is errors when using ndpyramid with a dask PBSCluster at scale due to ESMF not being thread-safe (see pangeo-data/xESMF#307 (comment)).
To be clear: This still uses xESMF to generate the regridding weights, it just allows you to generate them once outside of dask and then use them repeatedly without invoking
xESMF
on you dask cluster, which is enough to get around the threading errors (because you can completely avoid importing xESMF on the dask worker at all).This notebook shows that this function gives the same results as using xESMF for the application of the weights.
I'm not expecting this to be merged - I just wanted to put it up here in case it's useful to anyone.