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

Follow-up for segment lists #5812

Open
4 of 10 tasks
philippotto opened this issue Nov 1, 2021 · 0 comments
Open
4 of 10 tasks

Follow-up for segment lists #5812

philippotto opened this issue Nov 1, 2021 · 0 comments

Comments

@philippotto
Copy link
Member

philippotto commented Nov 1, 2021

Detailed Description

See #4667.

  • Naming cells
  • Compute segment list on-the-fly while navigating through a dataset (list could be ephemeral, so that we can also cope with huge datasets)
  • Detect if anchor position of segment got out of sync #6530
  • Statistics, such as amount of voxels (probably computed ad-hoc) Use segment statistics routes in frontend #7145
  • Locking a cell (so that it cannot be mutated)
  • Allow to compute a segment list for a given bounding box
  • Use Case: Nuclei Detector should emit segmentation along with segment list
    • How exactly should we approach this?
  • Hide certain segment ids (can be done via mappings, but what if a mapping already exists?

Context

  • Specific to long-running jobs (set jobsEnabled=true in application.conf)
  • Specific to webKnossos.org (set isDemoInstance=true in application.conf)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant