Detach SpatialData object from its Zarr store
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Is there an easy way to detach a SpatialData object from its Zarr store? Say I have a smallish object that fits into memory and I want to make some experimental changes without possibly changing the data on disk, what is the recommended workflow? Thanks in advance!
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
The issue names no files, tests, or entry points. First clarify whether the expected outcome is a detach or copy workflow, then identify the relevant SpatialData and Zarr-store handling code; done should include a documented, tested way to make in-memory experimental changes without modifying the store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100