You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having a segmentation layer with uint32 or uint64 the segment id 2 ** 32 - 1 is rendered completely white (also overwriting the color layer), as this value is reserved as EMPTY_KEY_VALUE for the cuckoo hashing table.
The segment should be rendered as usual. To fix this, I propose to set the EMPTY_KEY_VALUE = 0 as 0 means eraser for segmentation layers anyway. But EMPTY_KEY_VALUE = 0 should only be set for the custom color cuckoo hash table, not for the once used for color layers.
Current Behavior
See image above.
Steps to Reproduce the bug
Open a dataset with segmentation layer uint32 (e.g. l4_sample)
Set the segmentation id manually to 2 ** 32 - 1 = 4294967295 and draw around.
The drawn area should be completely white everywhere
The text was updated successfully, but these errors were encountered:
Context
When having a segmentation layer with uint32 or uint64 the segment id
2 ** 32 - 1
is rendered completely white (also overwriting the color layer), as this value is reserved asEMPTY_KEY_VALUE
for the cuckoo hashing table.Discussion in slack
Expected Behavior
The segment should be rendered as usual. To fix this, I propose to set the
EMPTY_KEY_VALUE = 0
as0
means eraser for segmentation layers anyway. ButEMPTY_KEY_VALUE = 0
should only be set for the custom color cuckoo hash table, not for the once used for color layers.Current Behavior
See image above.
Steps to Reproduce the bug
2 ** 32 - 1 = 4294967295
and draw around.The text was updated successfully, but these errors were encountered: