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

z_index = 0 for polygons in MERSCOPE #256

Open
LucaMarconato opened this issue Jan 5, 2025 · 3 comments
Open

z_index = 0 for polygons in MERSCOPE #256

LucaMarconato opened this issue Jan 5, 2025 · 3 comments

Comments

@LucaMarconato
Copy link
Member

          This commit seems to solve my issue reported here: https://github.com/scverse/spatialdata-io/issues/208

Is there a reason why only polygons from z_index = 0 are kept? By default the reader select plane z=3.

Originally posted by @MathieuBo in #207 (comment)

@LucaMarconato
Copy link
Member Author

@quentinblampey do you have any thought on this? (please see the linked discussion).

@pakiessling
Copy link

The Merscope on-board software only performs segmentation on one z-level and saves these polygons for z-indeces 0-6, using the vizgen postprocessing software users have the ability to segment every z-level separately.

I think it would make the most sense to default to the same z-level for polygons and images and give the user the option to choose which z-levels should be loaded.

@quentinblampey
Copy link
Contributor

z_index = 0 was used because the polygons are duplicated for all z-indices. I was not aware of the possibility of segmenting every z-level using VPT, thanks for letting us know @pakiessling! In that case, I agree that it makes sense to let the user decide

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