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

"Segment ID at position" can be wrong in certain conditions #4431

Closed
philippotto opened this issue Feb 3, 2020 · 1 comment · Fixed by #4480
Closed

"Segment ID at position" can be wrong in certain conditions #4431

philippotto opened this issue Feb 3, 2020 · 1 comment · Fixed by #4480
Assignees

Comments

@philippotto
Copy link
Member

Link to Discuss

  • disable “render missing data black”
  • have segmentation in mag2
  • zoom into mag1
  • hovering over a segment does say "null"
@philippotto
Copy link
Member Author

From Alessandro:

Thinking about it: The most elegant solution would be to always report the ID of the segment that is show at the center of the view port, and show the corresponding magnificant to avoid confusion. This likely is the “expected behavior” and has the additional benefit that it piggy-packs on the progressing loading strategy. The segment ID for large processes (e.g., diameter) can be read out much earlier than if one has to wait until the highest-resolution segmentation is loaded.

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

Successfully merging a pull request may close this issue.

2 participants