Slicer3:Module:LabelBinaryImages-Documentation - Revision history

Bikekilic at 18:28, 28 August 2008

2008-08-28T18:28:50Z

Bikekilic: /* Future work */

2008-08-28T18:22:35Z

Future work

Bikekilic at 18:20, 28 August 2008

2008-08-28T18:20:26Z

Bikekilic at 18:12, 28 August 2008

2008-08-28T18:12:00Z

Bikekilic: /* Results&Comments */

2008-08-28T18:05:56Z

Results&Comments

Bikekilic at 18:03, 28 August 2008

2008-08-28T18:03:21Z

Bikekilic: /* Results&Comments */

2008-08-28T16:23:05Z

Results&Comments

Bikekilic at 16:21, 28 August 2008

2008-08-28T16:21:18Z

Bikekilic: /* Screen shots */

2008-08-28T16:14:44Z

Screen shots

Bikekilic: /* Screen shots */

2008-08-28T16:12:56Z

Screen shots

← Older revision		Revision as of 18:28, 28 August 2008
Line 1:		Line 1:
		+	[[Documentation\|Return to Slicer Documentation]]
		+
	==Binary Thresholding and Labeling==		==Binary Thresholding and Labeling==

@@ Line 69: / Line 69: @@
 ===Future work===
-As a future work, it will be better to add an algorithm which makes label mapping in LabelBinaryImages module instead of using Editor module in Slicer 3. The reason is that the thresholding in Editor module and the one in LabelBinaryImages module works different so creating label maps and then coloring these maps with different labels fails by using Editor module. In 2D plane, I can see that the labels after separation of spheres by erosion processes do not change even they overwrite after many dilation processes. However, when I want to color these different labeled objects, at that point I can not achieve my goal and am not be able to see the result in 3D space.
+As a future work, it will be better to add an algorithm which makes label mapping in LabelBinaryImages module instead of using Editor module in Slicer 3. The reason is that the thresholding in Editor module and the one in LabelBinaryImages module works different so creating label maps and then coloring these maps with different labels fails by using Editor module. In 2D plane, I can see that the labels which are defined by LabelBinaryImages module by performing on the separated binary spheres after erosion processes do not change even they overwrite after many dilation processes. However, when I want to color these different labeled objects, at that point I can not achieve my goal and am not be able to see the result in 3D space.
 ===References===

← Older revision		Revision as of 18:20, 28 August 2008
Line 68:		Line 68:

	===Future work===		===Future work===
		+
		+	As a future work, it will be better to add an algorithm which makes label mapping in LabelBinaryImages module instead of using Editor module in Slicer 3. The reason is that the thresholding in Editor module and the one in LabelBinaryImages module works different so creating label maps and then coloring these maps with different labels fails by using Editor module. In 2D plane, I can see that the labels after separation of spheres by erosion processes do not change even they overwrite after many dilation processes. However, when I want to color these different labeled objects, at that point I can not achieve my goal and am not be able to see the result in 3D space.
		+
		+

	===References===		===References===

← Older revision		Revision as of 18:12, 28 August 2008
Line 66:		Line 66:

	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, when I entered 255 for dilate value to dilate the output image of LabelBinaryImages module, there was no change in the output image. However, when I chose 1 or 2 for the dilate value, the image has been dilated by given structuring element. In my opinion, the reason is that the output of LabelBinaryImages module is formed by the label values 0, 1 and 2, whereas the output of BinaryThresholding module has 255 inside and 0 outside.		What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, when I entered 255 for dilate value to dilate the output image of LabelBinaryImages module, there was no change in the output image. However, when I chose 1 or 2 for the dilate value, the image has been dilated by given structuring element. In my opinion, the reason is that the output of LabelBinaryImages module is formed by the label values 0, 1 and 2, whereas the output of BinaryThresholding module has 255 inside and 0 outside.
		+
		+	===Future work===
		+
		+	===References===
		+
		+	#Ibanez L., Schroeder W.,Ng L. & Cates J., The ITK Software Guide Second Edition Updated for ITK Version 2.4, 2005.
		+	#Lehmann G.,''Label object representation and manipulation with ITK'', 2007. [http://www.insight-journal.com/]

← Older revision		Revision as of 18:05, 28 August 2008
Line 65:		Line 65:
	In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.		In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.

−	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, when I entered 255 for dilate value to dilate the output image of LabelBinaryImages module, there was no change in the output image. However, when I chose 1 or 2 for the dilate value, the output is ~~like as seen in ''Screen shots'' part above~~.	+	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, when I entered 255 for dilate value to dilate the output image of LabelBinaryImages module, there was no change in the output image. However, when I chose 1 or 2 for the dilate value, the image has been dilated by given structuring element. In my opinion, the reason is that the output of LabelBinaryImages module is formed by the label values 0, 1 and 2, whereas the output of BinaryThresholding module has 255 inside and 0 outside.

← Older revision		Revision as of 18:03, 28 August 2008
Line 65:		Line 65:
	In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.		In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.

−	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, ~~even~~ I ~~perform dilation on~~ the output image of LabelBinaryImages module	+	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, when I entered 255 for dilate value to dilate the output image of LabelBinaryImages module, there was no change in the output image. However, when I chose 1 or 2 for the dilate value, the output is like as seen in ''Screen shots'' part above.

← Older revision		Revision as of 16:23, 28 August 2008
Line 65:		Line 65:
	In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.		In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.

−	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments,	+	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments, even I perform dilation on the output image of LabelBinaryImages module

← Older revision		Revision as of 16:21, 28 August 2008
Line 58:		Line 58:

	As we keep on dilating the image, the spheres are still labeled as 1 and 2 and the background as 0.		As we keep on dilating the image, the spheres are still labeled as 1 and 2 and the background as 0.
		+
		+	==MORE INFORMATION==
		+
		+	===Results&Comments===
		+
		+	In this part, I tried to explain if we are able to use LabelBinaryImages module in morphological operations. What I have seen after using this module is that even I continue on dilation of the separated images and make them overwritten, the labels of the objects does not change. The label numbers remain the same as I had seen after I performed the algorithms in LabelBinaryImages module on the last eroded image.
		+
		+	What the user should be careful is that if user has the output of BinaryThresholding module as an input for BinaryDilateOperations module, the dilate value should be chosen as 255. However, if user chooses the output of LabelBinaryImages module as an input for dilation, the dilate value should be the same as label numbers. The reason is that as I have seen from my experiments,

← Older revision		Revision as of 16:14, 28 August 2008
Line 55:		Line 55:
	\|}		\|}

−	In the first square, the output of dilation by using BinaryDilateOperations module and label mapping by using Editor module can be seen. Second one indicates the output of LabelBinaryImages module. As mentioned in the section ''Module Description'' in this page, the background is labeled as 0 whereas the separated spheres are labeled as 1 and 2 consecutively.	+	In the first square, the output of dilation by using BinaryDilateOperations module and label mapping by using Editor module can be seen. Second one indicates the output of LabelBinaryImages module. As mentioned in the section ''Module Description'' in this page, the background is labeled as 0 whereas the separated spheres are labeled as 1 and 2 consecutively.
		+
		+	As we keep on dilating the image, the spheres are still labeled as 1 and 2 and the background as 0.

← Older revision		Revision as of 16:12, 28 August 2008
Line 54:		Line 54:
	\|[[Image:LabelingTrial.png\|thumb\|400px\|The output of LabelBinaryImagesModule and then dilation]]		\|[[Image:LabelingTrial.png\|thumb\|400px\|The output of LabelBinaryImagesModule and then dilation]]
	\|}		\|}
		+
		+	In the first square, the output of dilation by using BinaryDilateOperations module and label mapping by using Editor module can be seen. Second one indicates the output of LabelBinaryImages module. As mentioned in the section ''Module Description'' in this page, the background is labeled as 0 whereas the separated spheres are labeled as 1 and 2 consecutively.