We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Similar to the downsample button, this would internally use the duplicate route and replace the tracing id in the annotation layer.
Would need a new route on webknossos backend side that forwards this to tracingstore (should be quick to do)
Note that this is currently only possible for volume annotations with no fallback segmentation layer
The text was updated successfully, but these errors were encountered:
unassigning myself as the backend part is done
Sorry, something went wrong.
Is there a way to know whether a volume tracing has a segment index?
@MichaelBuessemeyer This is probably quick to do and could be something for you in this sprint. I imagine an entry in the layer dropdown.
Yes, see VolumeTracing.proto, optional bool hasSegmentIndex
optional bool hasSegmentIndex
MichaelBuessemeyer
Successfully merging a pull request may close this issue.
Similar to the downsample button, this would internally use the duplicate route and replace the tracing id in the annotation layer.
Would need a new route on webknossos backend side that forwards this to tracingstore (should be quick to do)
Note that this is currently only possible for volume annotations with no fallback segmentation layer
The text was updated successfully, but these errors were encountered: