[Insight-developers] Problems with recent change to QuadEdgeMesh filters

[Luis Ibanez]

Hi Bill,

Thanks for tracking the problem,
Please feel free to go ahead and commit the fix.


     Luis


---------------------
Bill Lorensen wrote:
> Luis,
> 
> I found the problem.
> 
> The statement:
> 
> mesh = this->GetOutput()
> should be replaced with something like:
>       this->CopyMeshToMesh(this->GetInput(), mesh);
> where
>    OutputMeshPointer mesh = OutputMeshType::New();
> 
> CopyMeshToMesh should be added to  QuadEdgeMeshToQuadEdgeMeshFilter
> 
> I suspect other changes you made will cause similar problems.
> 
> If you (and Alex) agree, I can make these changes. I'll check the
> output of the tests with paraview to verify they are OK.
> 
> Bill
> 
> 
> On Tue, Sep 22, 2009 at 12:01 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> 
>>Luis,
>>
>>valgrind picked up some problems with itkQuadEdgeMeshSmoothingTest0
>>http://www.cdash.org/CDash/viewDynamicAnalysisFile.php?id=419453
>>
>>I'm pretty sure these problems are a result of your recent changes to
>>itkQuadEdgeMeshSmoothing.
>>
>>In tracking down the valgrind issues, I ran
>>itkQuadEdgeMeshSmoothingTest0 locally and noticed that the output it
>>produces is not correct, at least on my system. The test produces a
>>mesh that has 1307 identical points and not polydata.
>>
>>Bill
>>
> 
>