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

Multicut: option to keep one team of annotations (red or blue) for next split at the same location #538

Open
szichieh opened this issue Apr 2, 2021 · 2 comments

Comments

@szichieh
Copy link

szichieh commented Apr 2, 2021

At a messy location that requires multiple splits, it would be great that we have the option to keep the annotations in the neuron of interest from one split to another. So those annotations would not need to be placed over and over again.
It would be even better that one of the team could cut off multiple mergers at once. Or in a simpler way to have extra team(s)/color(s) to label more merger.

requesting on behalf of tracers

@ceesem
Copy link

ceesem commented Apr 14, 2021

Agreed, this would be nice!

On a similar vein of improving multicut location points, being able to delete points from within the multicut point list would be much more convenient than having to select them and then go to the lower right corner. This is particularly true due to misplaced points that occur due to the bug in #503 or when one uses the wrong color due to #519.

@manuel-castro manuel-castro self-assigned this May 13, 2021
@manuel-castro
Copy link

manuel-castro commented Jul 23, 2021

What's required for this feature is for the ChunkedGraph to return the new root IDs that are created after a split in a specific order -- for example the "red ID" first and the "blue ID" second. The reason this is needed is because each point in the multicut tool is associated with a specific root ID, so after the ChunkedGraph splits a specific root and returns two (or more) new IDs, we need to know which ID is the "blue ID" and which is the "red ID" to reassign the multicut points. Unfortunately I didn't have time to get to this.

@manuel-castro manuel-castro removed their assignment Jul 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants