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
The problem is exactly as written in closed issue #9862, but I'm using:
xarray: 2025.1.2
dask: 2025.2.0
Since everything is the same (including traceback and behavior when pasted into console or binder), please refer to original issue for complete description.
I didn't click "new issue" since it's an old issue that was closed, but is not fixed.
What did you expect to happen?
We would expect the rolling mean to calculate correctly.
Minimal Complete Verifiable Example
importdask.arrayasdaimportxarrayasxrimportnumpyasnp# Dimensions and sizesnx, ny, nt=100, 200, 50# size of x, y, and time dimensionsx=np.linspace(0, 10, nx) # x-coordinatesy=np.linspace(0, 20, ny) # y-coordinatestime=np.linspace(0, 1, nt) # time coordinates# Generate a random Dask array with lazy computationdata=da.random.random(size=(nx, ny, nt), chunks=(100, 200, 1))
# Create an xarray DataArray with coordinates and attributesdata_array=xr.DataArray(
data,
dims=["x", "y", "time"],
coords={"x": x, "y": y, "time": time},
name="dummy_data",
attrs={"units": "arbitrary", "description": "Dummy 3D dataset"}
)
d_rolling=data_array.rolling(time=5).mean()
d_rolling.compute()
MVCE confirmation
Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
Complete example — the example is self-contained, including all data and the text of any traceback.
Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
New issue — a search of GitHub Issues suggests this is not a duplicate.
Recent environment — the issue occurs with the latest version of xarray and its dependencies.
Thanks for opening your first issue here at xarray! Be sure to follow the issue template!
If you have an idea for a solution, we would really welcome a Pull Request with proposed changes.
See the Contributing Guide for more.
It may take us a while to respond here, but we really value your contribution. Contributors like you help make xarray better.
Thank you!
What happened?
The problem is exactly as written in closed issue #9862, but I'm using:
Since everything is the same (including traceback and behavior when pasted into console or binder), please refer to original issue for complete description.
I didn't click "new issue" since it's an old issue that was closed, but is not fixed.
What did you expect to happen?
We would expect the rolling mean to calculate correctly.
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
Anything else we need to know?
No response
Environment
xarray: 2025.1.2
pandas: 2.2.3
numpy: 2.1.3
scipy: 1.15.2
netCDF4: 1.7.2
pydap: 3.5.3
h5netcdf: 1.5.0
h5py: 3.13.0
zarr: 2.18.3
cftime: 1.6.4
nc_time_axis: 1.4.1
iris: 3.11.0
bottleneck: 1.4.2
dask: 2025.2.0
distributed: 2025.2.0
matplotlib: 3.10.1
cartopy: 0.24.0
seaborn: 0.13.2
numbagg: 0.9.0
fsspec: 2025.2.0
cupy: None
pint: 0.24.4
sparse: 0.15.5
flox: None
numpy_groupies: None
setuptools: 75.8.0
pip: 25.0
conda: None
pytest: None
mypy: None
IPython: 8.32.0
sphinx: None
The text was updated successfully, but these errors were encountered: