Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiscales questions #17

Closed
tischi opened this issue Nov 28, 2020 · 7 comments
Closed

Multiscales questions #17

tischi opened this issue Nov 28, 2020 · 7 comments

Comments

@tischi
Copy link

tischi commented Nov 28, 2020

@joshmoore @will-moore
Multiscales is an array: Multiscale[] multiscales = n5.getAttribute( "", "multiscales", Multiscale[].class );
I don't understand in which scenarios this array could have more than one item?

@joshmoore
Copy link
Member

The primary use case at the moment (the one listed in the spec) is multiple different downsamplings. A base image with two multiscales each with a different scale or a different method. There's no need for the two multiscales to have the same base though. So it would also allow you to just have two pyramids (in our jargon) in the same zgroup.

Note: moving this issue to the new repo.

@joshmoore joshmoore transferred this issue from ome/omero-ms-zarr Nov 28, 2020
@tischi
Copy link
Author

tischi commented Nov 28, 2020

@joshmoore

Thanks! I guess for opening this in BDV we for now just pick multiscales[ 0 ], ok?
Implementing a good logic for opening alternative pyramids feels like a more complex project to me.

@joshmoore
Copy link
Member

Agreed.

@constantinpape
Copy link
Contributor

This is a very old discussion, so I am closing this.

@joshmoore
Copy link
Member

Thanks for the clean up, @constantinpape. I think the use of the multiple multiscales is still not well formulated (see question during the 6th NGFF call) but happy for that to be in a follow-up issue/PR.

@constantinpape
Copy link
Contributor

@joshmoore my strategy right now is just to collect all the "low hanging fruit" follow ups in #86 and then spin off issue(s) from that one as soon as 0.4 is released - could you just leave a comment there regarding the multiple multiscales?

@joshmoore
Copy link
Member

Perfect strategy. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants