[Insight-users] Kappa Sigma Clipping typedef error
Oleksandr Dzyubak
adzyubak at gmail.com
Thu Jul 10 12:41:50 EDT 2008
Hi Luis,
Of course, with my greatest pleasure I will write a review.
Thanks to Gaetan for his contribution.
Regards
Alex
Luis Ibanez wrote:
>
>
> Hi Alex,
>
>
> Thanks for letting us know that the filter works for you.
>
> and Thanks to Gaetan for this nice contribution to the Insight Journal.
>
>
>
> A humble request:
>
> Could you please write a short review for Gaetan's paper ?
>
>
>
> Thanks
>
>
> Luis
>
>
> -------------------------
> Oleksandr Dzyubak wrote:
>> Hi Luis,
>>
>> I have rebuilt my ITK and tested the updated
>> version of the "Kappa Sigma Clipping" algorithm.
>>
>> Fantastic, works perfectly well and very fast.
>> Gaetan Lehmann, thanks for your contribution.
>>
>> Thanks all of you for your help and support,
>>
>> Alex
>>
>> Luis Ibanez wrote:
>>
>>>
>>> Hi Olkesandr,
>>>
>>> This classes contributeed by Gaetan Lehmann have now been included
>>> in the Insight/Code/Review directory in the main CVS trunk of ITK.
>>>
>>> If you want to try the new versions, please do the following:
>>>
>>> 1) Update your cvs Checkout
>>> 2) Rerun CMake on the binary directory of ITK
>>> 3) go to Advanced
>>> 4) enable the variable ITK_USE_REVIEW
>>> 5) configure and generate with CMake
>>>
>>>
>>> You will find a test under
>>>
>>>
>>> Insight/Testing/Code/Review
>>>
>>>
>>> that illustrates how you can set up the type of the output image.
>>>
>>>
>>>
>>> Please give it a try and let us know if you find any problems,
>>>
>>>
>>> Thanks
>>>
>>>
>>> Luis
>>>
>>>
>>> ------------------------
>>> Oleksandr Dzyubak wrote:
>>>
>>>> Dear ITKers,
>>>>
>>>> Some while ago I decided to test the Kappa Sigma Clipping algorithm
>>>> which
>>>> I downloaded from the Insight-journal web page.
>>>>
>>>> http://insight-journal.org/midas/handle.php?handle=1926/367
>>>>
>>>> In the paper which comes with an archive there is an explanation
>>>> how to use it and, in particular, the lines describing the types of
>>>> input/output images.
>>>>
>>>> ***********Begin code snippet*********
>>>> const int dim = 3;
>>>>
>>>> typedef unsigned char PType;
>>>> typedef itk::Image< PType, dim > IType;
>>>> typedef itk::ImageFileReader< IType > ReaderType;
>>>>
>>>> typedef itk::ImageFileWriter< IType > WriterType;
>>>> ***********End code snippet*********
>>>>
>>>> Of cousre, that is quite natural to keep an output segmented binary
>>>> image as an unsigned char type
>>>> but what about an input image. In my case I have input images in a
>>>> signed short format and
>>>> if I change the typedef for the input to signed short, I get an
>>>> error below.
>>>>
>>>> ******* Begin Error ************
>>>>
>>>> dzyubak at debian: /BUILD$ make
>>>> Scanning dependencies of target check
>>>> [100%] Building CXX object CMakeFiles/check.dir/check.cxx.o
>>>> /mnt/Public/ITK_Test/Kappa_Sigma_Clipping/Src/check.cxx: In
>>>> function 'int main(int, char**)':
>>>> /mnt/Public/ITK_Test/Kappa_Sigma_Clipping/Src/check.cxx:42: error:
>>>> no matching function for call to
>>>> 'itk::ImageFileWriter<itk::Image<unsigned char, 3u>
>>>> >::SetInput(itk::Image<short int, 3u>*)'
>>>> /usr/local/include/InsightToolkit/IO/itkImageFileWriter.txx:56:
>>>> note: candidates are: void
>>>> itk::ImageFileWriter<TInputImage>::SetInput(const TInputImage*)
>>>> [with TInputImage = itk::Image<unsigned char, 3u>]
>>>> make[2]: *** [CMakeFiles/check.dir/check.cxx.o] Error 1
>>>> make[1]: *** [CMakeFiles/check.dir/all] Error 2
>>>> make: *** [all] Error 2
>>>> dzyubak at debian: /BUILD$
>>>>
>>>> ******* End Error ************
>>>>
>>>>
>>>> Does this mean that the algorithm can only work if the input type
>>>> matches the output?
>>>> If it does, then I have to extend the pipeline so to include the
>>>> rescaler, right?
>>>>
>>>> I would appreciate any help on this matter.
>>>>
>>>> Thanks,
>>>>
>>>> Alex
>>>> _______________________________________________
>>>> Insight-users mailing list
>>>> Insight-users at itk.org
>>>> http://www.itk.org/mailman/listinfo/insight-users
>>>>
>>
>>
More information about the Insight-users
mailing list