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 think boundary should be +inf, and then, to keep the same behaviour, one would have to keep the whole camera if the number of surviving pixels is above a threshold (500 by default).
The algo is very simple, so I am not sure it pays to use more generic functions - with the additional calls, wouldn't it be slower?
Function
get_selected_pixels
selects pixels above T pixels and keeps N rounds of pixels around.Could we use the existing function
zero_suppression_tailcut_dilation
with parameters?
The text was updated successfully, but these errors were encountered: