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

Add locking to focused merging to prevent conflicts with supervoxel splitting #307

Open
hubbardp opened this issue Feb 7, 2019 · 0 comments
Assignees
Labels

Comments

@hubbardp
Copy link
Member

hubbardp commented Feb 7, 2019

The Neu3 cleaving tool uses the Librarian to check out (lock) the body being cleaved. All current work on supervoxel splitting is being done through the cleaving tool, so the bodies of all supervoxels being split are being locked.

So the Neu3 focused merging tool should also use the Librarian to lock the bodies mapped from the two supervoxel in the merging task.

Doing so should prevent an odd problem that occurred today, which may be representative of other odd problems that are occurring recently. A user in the middle of a focused merging session reported that only one body was appearing for a particular task. The problem was that one of the supervoxels in that task no longer mapped to a body. It turns out that the supervoxel had been split, so its ID is no longer in use. The Neu3 code for the focused merging task checks for this situation, and skips the task if the mapping fails, but there is nothing to prevent the supervoxel from being split after the merging task has been started. Based on the logs, that is what happened in this case.

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

No branches or pull requests

1 participant