NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 680 - Skeletonize fails for vertical 2x3
Skeletonize fails for vertical 2x3
Status: ASSIGNED
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
PC Linux
: P5 normal
Assigned To: Ignacio Arganda
Depends on:
Blocks:
 
Reported: 2013-12-03 07:48 CST by Daniel Hornung
Modified: 2014-08-25 14:56 CDT
2 users (show)

See Also:


Attachments
Minimal example which makes Skeletonize fails. (1023 bytes, image/tiff)
2013-12-03 07:51 CST, Daniel Hornung

Description Daniel Hornung 2013-12-03 07:48:49 CST

    
Comment 1 Daniel Hornung 2013-12-03 07:51:06 CST
Created attachment 125
Minimal example which makes Skeletonize fails.
Comment 2 Daniel Hornung 2013-12-03 07:51:48 CST
When applying the Skeletonize plugin to more or less vertical structures of size 2x2, it finds no skeleton.  Such an image would be for example (each slice being the same):

0 0 0 0 0 0
0 0 0 0 0 0
0 0 1 1 0 0
0 0 1 1 0 0
0 0 0 0 0 0
0 0 0 0 0 0
Comment 3 Ignacio Arganda 2013-12-03 08:34:17 CST
Working on it.

ignacio
Comment 4 Daniel Hornung 2013-12-04 03:59:37 CST
Note:

A yet more minimal example suggesting that something may be wrong explicitly with the thinning from north or south:

0 0 0 0
0 0 0 0
0 1 1 0
0 0 0 0  -> fails

0 0 0 0
0 1 0 0
0 1 0 0
0 0 0 0  -> works
Comment 5 G. Landini 2013-12-04 04:46:54 CST
I wonder if that this is because the pixel removal needs to start somewhere and so this might a consequence of scanning the region in a particular way.

The IJ 2D skeleton has this characteristic too (try with a 2x2 region) you end up with a horizontal bar at the top, while there are potentially 4 different skeletons which are all correct.

This pattern ends in a point:
xx
xx
x

but this one ends in a 2x1 line:

xx
xx

and the point result above is different from "ultimate points" result.
Comment 6 Ignacio Arganda 2013-12-04 05:54:55 CST
All thinning methods start scanning from one side, which means they will give you a different result if you rotate your image for example. However this bug is something else, it should never remove a single voxel. I'll try to work on it in the next few weeks.
Comment 7 Daniel Hornung 2013-12-04 07:52:34 CST
> However this bug is something else, it should never remove a single voxel.

Well, of course it should remove some voxels so that each xy slice contains at most a single white voxel.
Comment 8 Ignacio Arganda 2013-12-04 07:59:57 CST
You misunderstood me, what I meant is the algorithm should never remove a voxel if it is the only one that is still not deleted during the scanning. I will check if a condition is missing.