Rechunk dask image if not using multi-scales
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Hello,
In the documentation here, Image2DModel.parse has a chunks argument. Contrary to what suggests the documentation, this argument is only used when creating a MultiscaleSpatialImage
I was expecting that it would be also applied on SpatialImage (via image.rechunk), so I was wondering if this is a bug or just a lack of clarity in the doc?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Image2DModel documentation and the Image2DModel.parse entry point. Compare how the chunks argument is handled for SpatialImage and MultiscaleSpatialImage, then determine whether the behavior or the documentation should change. Done means the chunks behavior is consistent with the documented contract.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100