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
Fix behaviour of min_count in reducing functions (#4911)
* Add more tests for reducing functions with min_count
* Make sure Dask-backed arrays are not computed.
* Check some specific examples give the correct output.
* Run membership tests on xarray.core.dtypes.NAT_TYPES
* Fix behaviour of min_count in reducing functions.
* Fix mask checks in xarray.core.nanops._maybe_null_out to run lazily
for Dask-backed arrays.
* Change xarray.core.dtypes.NAT_TYPES to a set (it is only used for
membership checks).
* Add dtypes to NAT_TYPES rather than instances. Previously np.float64
was returning true from `dtype in NAT_TYPES` which resulted in
min_count being ignored when reducing over all axes.
* Add whatsnew entry.
* Improvements from review.
* use duck_array_ops.where instead of np.where
* add docstring and whatsnew messages about sum/prod on integer arrays
with skipna=True and min_count != None now returning a float array.
Co-authored-by: Deepak Cherian <[email protected]>
0 commit comments