When trying to identify secondary objects using the propagation algorithm, sometimes part of the cell border seems to be encountering an invisible boundary. I thought this may be due to the gradient of the input image, but even if I binarize the image prior to the identifysecondaryobjects module, the borders are still fixed.
I’ve only noticed this when the cell area (but not the object boundaries) is touching the edge of the image
Changing the regularization factor can make the border more zig-zag or straight-lined, but does not significantly change the general location of the border
Changing the threshold correction factor does not change the boundary
There is no reason why the border should be drawn here. There are no other objects taking up this space, and there is no gradient (in the binary image) and could be responsible for the borders. Any thoughts on what this could be?
I’ve attached a short pipeline and image set to demonstrate this. This pipeline was created in 2.1.1 but I’ve also noticed the same problem in 2.2.0
Pipeline211.cpproj (538.7 KB)
Here is what I get when I run the pipeline. The east/south borders are basically “fixed”.