Difference between revisions of "Projects/Slicer3/2007 Project Week EdgeDetection"
From NAMIC Wiki
| Line 5: | Line 5: | ||
{| | {| | ||
|[[Image:ZeroCrossingBasedEdgeDetectionFilterScreenShot.JPG|thumb|320px|AFTER!]] | |[[Image:ZeroCrossingBasedEdgeDetectionFilterScreenShot.JPG|thumb|320px|AFTER!]] | ||
| + | |[[Image:LuisAndElliot.jpg|thumb|320px|Working hard on ITK and Slicer3]] | ||
|} | |} | ||
| − | |||
__NOTOC__ | __NOTOC__ | ||
| Line 51: | Line 51: | ||
<br style="clear: both;" /> | <br style="clear: both;" /> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 00:19, 29 June 2007
Home < Projects < Slicer3 < 2007 Project Week EdgeDetection Return to Project Week Main Page |
Key Investigators
- MIT: Elliot Uvero
- BWH: Lauren O'Donnell
- Kitware: Luis Ibanez
Objective
Enable edge detection of images in Slicer3.
Approach, Plan
Create a Slicer3 CLP module for edge detection of images, using ITK filters.
Progress
A CLP module, Zero Crossing Based Edge Detection, has been developed in Slicer3. With the great help of Luis, the documentation and error checking of the ITK ZeroCrossingEdgeDetectionFilter were improved, and the concept checking was improved to make sure that the pixel type is float or double.
Conclusions and Findings
- Concept checking should be set to ON in CMake when ITK is configured.
- When off (default) there is no check that input/output image is the same type for the itkZeroCrossingEdgeDetectionFilter.
- Currently the itkZeroCrossingEdgeDetectionFilter appears to function correctly with float and double input.
- Short input produces different edge output.
