forked from google/neuroglancer
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Multicut: Not recognizing my selected supervoxels properly #564
Comments
chrisj
pushed a commit
that referenced
this issue
Apr 2, 2024
…ce (#564) Bumps [express](https://github.com/expressjs/express) from 4.18.3 to 4.19.2. - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/master/History.md) - [Commits](expressjs/express@4.18.3...4.19.2) --- updated-dependencies: - dependency-name: express dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. I'd like to report a weird bug I'm facing with multicut, which its split preview does not recognize the points I selected. So far this only happens when I am proofreading/multicutting objects using ctrl + shift + left-click to refresh. This does not happen when I often refresh my browser tab entirely. Also, Neuroglancer will recognize correct inputs after refreshing the browser tab.
Here is one of these situations. Even though I selected two supervoxels, Neuroglancer is recognizing three instead of two. I actually used three supervoxels to multicult different sections of different neurons before this procedure, so maybe these "three" inputs are related to the previous ones.
The text was updated successfully, but these errors were encountered: