Do not convert arrays to dask
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Currently, arrays for labels, images, etc. are required to be dask arrays. This makes sense when loading data from a store, but doesn't make sense to me when creating in memory (e.g. spatialdata.models.Labels2DModel.parse(np.array([[0, 0], [0, 0]]), dims=["y", "x"]))
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 at spatialdata.models.Labels2DModel.parse and trace how the provided NumPy array is handled when creating an in-memory model. Confirm the desired behavior for in-memory arrays versus arrays loaded from a store, then verify that the relevant model behavior and existing tests preserve the expected array type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100