summary refs log tree commit diff
path: root/pbmclean.html
diff options
context:
space:
mode:
authorgiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2011-12-31 00:42:10 +0000
committergiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2011-12-31 00:42:10 +0000
commitc66acd4437d9554996fca9e87f9dff946e143654 (patch)
tree9c50fc30fc72c190f6aba8eee1c52d7608766ee6 /pbmclean.html
parent0471feecc263a7ce7d9233b4792a9865e80e6937 (diff)
downloadnetpbm-mirror-c66acd4437d9554996fca9e87f9dff946e143654.tar.gz
netpbm-mirror-c66acd4437d9554996fca9e87f9dff946e143654.tar.xz
netpbm-mirror-c66acd4437d9554996fca9e87f9dff946e143654.zip
miscellaneous update
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@1618 9d0c8265-081b-0410-96cb-a4ca84ce46f8
Diffstat (limited to 'pbmclean.html')
-rw-r--r--pbmclean.html11
1 files changed, 0 insertions, 11 deletions
diff --git a/pbmclean.html b/pbmclean.html
index ab965e1f..35efa4e3 100644
--- a/pbmclean.html
+++ b/pbmclean.html
@@ -52,17 +52,6 @@ isolated.
 black pixels in an otherwise white field, each of those pixels is isolated,
 so <b>pbmclean</b> erases them - turns both white.
 
-<p>But it isn't that simple, because as <b>pbmclean</b> progresses, its having
-erased a pixel may make another pixel isolated that isn't isolated in the
-original image.  Consider a straight vertical line of 4 pixels, with
-<b>-minneigbors</b> of two.  <b>pbmclean</b> considers the top pixel first, and
-finding that it has only one neighbor (the pixel below it), erases it.  The it
-considers the second pixel, and erases it for the same reason, even though it
-has two neighbors in the original image.  In this way, <b>pbmclean</b>
-ultimately erases the entire line.  Because of this weirdness, you probably
-don't want <b>-minneighbors</b> greater than one.  But you may want to run
-<b>pbmclean</b> multiple times with <b>-minneighbors</b> of one.
-
 <P>The default minimum 1 pixel &mdash; <b>pbmclean</b> flips only completely
 isolated pixels.