You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of #301 we return a numpy array when data is missing, to prevent a situation where when you computed the array you got a dask array back.
However, the upshot of this is that dask appears to un-broadcast the array, so you require the full memory allocation of the array to compute an array with no data in it.
This is very inefficient.
We should see if there is a way to generate a dask array which uses much less memory for some or all NaNs.
The text was updated successfully, but these errors were encountered:
As of #301 we return a numpy array when data is missing, to prevent a situation where when you computed the array you got a dask array back.
However, the upshot of this is that dask appears to un-broadcast the array, so you require the full memory allocation of the array to compute an array with no data in it.
This is very inefficient.
We should see if there is a way to generate a dask array which uses much less memory for some or all NaNs.
The text was updated successfully, but these errors were encountered: