For large images, handling overlaps at the post-processing stage can take many minutes.
It would be good to try to reduce this.
There's a strong chance that this can only be fixed in core QuPath (probably here), but I mention the issue here since running InstanSeg is currently the most obvious place where anyone will see that bottleneck.
For large images, handling overlaps at the post-processing stage can take many minutes.
It would be good to try to reduce this.
There's a strong chance that this can only be fixed in core QuPath (probably here), but I mention the issue here since running InstanSeg is currently the most obvious place where anyone will see that bottleneck.