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
I ran into this issue, which prevented me from segmenting. This is potentially an issue, given how clunky it is to delete doodles ...
Is it a problem for doodling outside the window? How can we get around this constraint? It is a nice feature of Dash-Doodler that one can label over the edges to ensure the pixels near the edge are labeled
... and the code still ran fine, giving me a good output. So, is there a specific reason to prevent the user segmenting the image if doodles are outside the image?
The text was updated successfully, but these errors were encountered:
Hey Dan, I wasn't sure the segmentation algorithm handled that properly hence that defensive approach. As it seems it can cope with that well I'll just remove that guard, thanks for the feedback.
I ran into this issue, which prevented me from segmenting. This is potentially an issue, given how clunky it is to delete doodles ...
Is it a problem for doodling outside the window? How can we get around this constraint? It is a nice feature of Dash-Doodler that one can label over the edges to ensure the pixels near the edge are labeled
If I uncomment th code block starting on this line ...
https://github.com/pyviz-topics/holodoodler/blob/70ec3078d7257a4c468bf6e35ef58fe5f7369416/doodler/components.py#L545
... and the code still ran fine, giving me a good output. So, is there a specific reason to prevent the user segmenting the image if doodles are outside the image?
The text was updated successfully, but these errors were encountered: