add _top_level to UserUpdateSegmentation and UserDeleteNodes to support copying of labels - #271
Open
AnniekStok wants to merge 4 commits into
Open
add _top_level to UserUpdateSegmentation and UserDeleteNodes to support copying of labels#271AnniekStok wants to merge 4 commits into
AnniekStok wants to merge 4 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #271 +/- ##
=======================================
Coverage 93.92% 93.92%
=======================================
Files 59 59
Lines 3323 3326 +3
=======================================
+ Hits 3121 3124 +3
Misses 202 202 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some copy label actions are both painting and erasing at the same time, on different regions. They replace the clicked node entirely, but only write on some of the original pixels. Since the UserUpdateSegmentation action can only paint with exactly one value, this becomes two actions. In order to undo both actions in one go, we need the
_top_levelargument, so we can stack them together.For motile tracker PR funkelab/motile_tracker#477