home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 384449698

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
384449698 MDU6SXNzdWUzODQ0NDk2OTg= 2576 When is transpose not lazy? 1828519 closed 0     1 2018-11-26T18:10:36Z 2019-03-12T15:01:18Z 2019-03-12T15:01:18Z CONTRIBUTOR      

Code Sample, a copy-pastable example if possible

```python import xarray as xr import dask.array as da from dask.diagnostics import ProgressBar a = xr.DataArray(da.zeros((3, 5, 5), chunks=(1, 2, 2)), dims=('bands', 'y', 'x'))

with ProgressBar(): b = a.transpose('y', 'x', 'bands')

dask does not show a progress bar due to no computation

with ProgressBar(): b = a.transpose('y', 'x', 'bands') b.compute()

dask computes the array (since we told it to) and we see a progress bar

```

Question

The documentation for transpose says that it is not lazy. Is this only in certain situations? By not lazy does it mean that when the data is computed that the transpose task will require all data to be loaded at once (one large chunk) or does it mean that the transpose operation will immediately compute the transposed array? My test above does not seem to compute the data when transpose is called.

Or is the documentation just outdated?

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2576/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed 13221727 issue

Links from other tables

  • 2 rows from issues_id in issues_labels
  • 1 row from issue in issue_comments
Powered by Datasette · Queries took 0.589ms · About: xarray-datasette