[Insight-users] setting parameters for GaussianBlurImageFunction

[Luis Ibanez]

Hi Phillip,

This problem has been fixed.

Bug # 464 was closed
http://www . itk . org/Bug/bug . php?op=show&bugid=464&pos=0

Set/Get methods were added for the member variables

    m_MaximumError
    m_MaximumKernelWidth
    m_UseImageSpacing

For the last variable, methods On/Off were also added.

This should now allow enough flexibility to command
the parameters of the internal GaussianOperator.

You will have to update your CVS checkout in order
to get this changes.


Please let us know if you find any problems.


Thanks


    Luis


-----------------------
Phillip Cheng wrote:
> Thanks Luis!  I appreciate your help, and I hope you're getting some kind of
> break during the holiday season!
> 
> I think it would also make sense to add Get/SetUseImageSpacing (or
> SetUseImageSpacingOn/Off) to GaussianBlurImageFunction as well.
> 
> Thanks,
> 
> Phillip
> 
> 
>>-----Original Message-----
>>From: Luis Ibanez [mailto:luis . ibanez at kitware . com]
>>Sent: Thursday, December 25, 2003 8:22 PM
>>To: Phillip Cheng
>>Cc: insight-users at itk . org
>>Subject: Re: [Insight-users] setting parameters for
>>GaussianBlurImageFunction
>>
>>
>>
>>Hi Phillip,
>>
>>I see your point now.
>>
>>You are right, the class is fixing the values of
>>the m_MaximumKernelWidth and the m_MaximumError
>>on the constructor and does not have Set/Get
>>methods for these two member variables.
>>
>>This has been entered as Bug # 464
>>http://www . itk . org/Bug/bug . php?op=show&bugid=464&pos=0
>>
>>The solution seems to be to simply add Set/Get
>>macros for these two member variables. It shouldn't
>>take too long to fix this.
>>
>>The possible lateral effects remain to be seen...
>>
>>
>>Regards,
>>
>>
>>   Luis
>>
>>
>>-------------------------
>>Phillip Cheng wrote:
>>
>>>Hi Luis,
>>>
>>>
>>>
>>>>The way to solve the warning is not to increase
>>>>the tolerance on the error, but to increase the
>>>>size (in pixels) of the kernel.
>>>
>>>
>>>Yes, but as you point out, large kernels will increase computation time
>>>(especially since I'm working with 3D images).  I think a
>>
>>tolerance of 0.001
>>
>>>will result in kernel sizes that are too large for my current needs.
>>>
>>>Incidentally, it's not documented what units SetExtent() is supposed to
>>>take.  From the code it looks like it's in multiples of sigma
>>
>>(rather than
>>
>>>units of pixels or distance)?
>>>
>>>
>>>
>>>>Just out of curiosity:
>>>>What is your criteria for selecting the sigma at each pixel ?
>>>
>>>
>>>The sigma I'm using depends on corresponding neighborhood
>>
>>information from a
>>
>>>segmented registered image.  This is part of some exploratory
>>
>>research for
>>
>>>partial volume correction on PET images.  The exact method of
>>
>>determining
>>
>>>sigma is part of the research question...
>>>
>>>Phillip
>>>
>>>_______________________________________________
>>>Insight-users mailing list
>>>Insight-users at itk . org
>>>http://www . itk . org/mailman/listinfo/insight-users
>>>
>>
>>
>>
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk . org
> http://www . itk . org/mailman/listinfo/insight-users
>