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
Exploring using morphological operations(i.e., erosions - cv2.erode() and dilations - cv2.dilate()) for removing ripples. So far this approach works well with images which have thinner ripple lines than scars.
2 erosions:
However, an opening - an erosion followed by a dilation (cv2.MORPH_OPEN) seems like the most promissing option.
This approach works best when the ripples are of 'thinner' line quality than the rest of the illustration. For example, this image has fairly homogenous line quality, and thus poor(ish) results:
Images with poorly connected lines do not work:
Images with lower than 300 dpi also perform very poorly (image is 200dpi).
The text was updated successfully, but these errors were encountered:
@crangelsmith This and issues with arrows may best be addressed by designing custom kernels derived from image proportions. I believe this data is already stored in teh algo that seperates profile, platform, and dorsal surface. We've briefly discussed this. I will open a new issu for this.
Exploring using morphological operations(i.e., erosions - cv2.erode() and dilations - cv2.dilate()) for removing ripples. So far this approach works well with images which have thinner ripple lines than scars.
2 erosions:
However, an opening - an erosion followed by a dilation (cv2.MORPH_OPEN) seems like the most promissing option.
This approach works best when the ripples are of 'thinner' line quality than the rest of the illustration. For example, this image has fairly homogenous line quality, and thus poor(ish) results:
Images with poorly connected lines do not work:
Images with lower than 300 dpi also perform very poorly (image is 200dpi).
The text was updated successfully, but these errors were encountered: