Hi Taylor, > I am using a real 2D image.
OK, I do not really understand, why you are not getting good results then. The original paper demonstrated good performance on 2D images. Maybe we need to look closer at that. The original paper shows results on the standard test image “MIT’s Cameraman”. Maybe it would help to compare this with your results. > That makes sense. Implementation-wise that sounds like a bit more work > though. Depending on the ITK default behaviour on the image boundary, it could be as simple as commenting out the calls to OverrideBoundaryCondition(&nbc) in itkTotalVariationSingleIterationImageFilter.txx and itkLocalVariationImageFilter.txx. > If I were to keep the existing approach the same, what part (or parts) of the > chain > needs to be generalized to work with 2D images? Everything I've seen so far > looks > fully templated wrt image type. The boundary conditions are the only issue I am familiar with so far. The implementation should be 2D-ready. At least I thought so, I did not tried it yet. > I haven't yet had a chance to study this closely though so I may be back with > more questions... I would be happy to hear more from your experiments. Best regards Klaus ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
