Currently considering only scale in the transformations for multiscales
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
As shown in the screenshot here, for multiscale images and multiscale labels we two sets of transformations. One at the top level, following the new NGFF specs, and one just between levels of the multiscale following the old specs.
Currently I am not saving the transformations in this format, I will have to adapt the IO to follow the NGFF specs (once they are approved), as described in this other issue: https://github.com/scverse/spatialdata/issues/114
But also in the code I am currently expecting the translation to always be absent. I believe that there is no need for that translation now that we have the new more powerful specs, so we'll have to discuss in the NGFF repo. For the moment I open this issue and I will ignore that.
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 by reviewing the NGFF transformation specifications and the related issue #114, then inspect the multiscale transformation and IO behavior described here. The work is complete when the approved NGFF format is implemented and the handling of translations between multiscale levels has been resolved.
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
- 25/100