[Insight-developers] Copy input to Output Mesh

[Arnaud GELAS]

Hi Michael,

I had the chance to read some parts of your code, and you can really
benefits in using itk::QuadEdgeMesh instead of using itk::Mesh for
filling the matrix.

Regarding this part, there is exactly the same piece of code in the
parameterization, that would be nice to extract that part from the
parameterization code in order to benefit from existing code. Then it
will only remain the part regarding the eigen-decomposition...

If you need help/guidance, it would be a real pleasure to help you in
this project.

Regards,
Arnaud


On Mon, 2009-11-23 at 12:14 -0500, Michel Audette wrote:
> Hi Michael, 
> 
> let me know if that works for you. I was aware of prior discussions on
> how to copy components of the mesh, and I was not aware of the history
> as to why there was no single function, so I was not able to make a
> useful contribution. 
> 
> In general, it's not a bad thing to copy to Insight Developers the way
> Luis has. Others, such as ITK contributors with particular expertise
> on these meshes, like Alexandre Gouillard and his collaborators, can
> chime in and make useful suggestions. I recognize that it's a public
> exercise in humility, and believe me, I empathize with this aspect of
> the learning curve, since I'm a fairly recent convert to ITK. 
> 
> Best wishes, 
> 
> Michel
> 
> On Sun, Nov 22, 2009 at 2:58 PM, Luis Ibanez <luis.ibanez at kitware.com>
> wrote:
>         Hi Michael,
>         
>         Yes, it will make sense to move (at least part) of the Copy
>         method
>         up to the MeshToMeshFilter class.
>         
>         Note that he basic methods that copy parts of the mesh were
>         already
>         there:
>         
>          void CopyInputMeshToOutputMeshPoints();
>          void CopyInputMeshToOutputMeshPointData();
>          void CopyInputMeshToOutputMeshCellLinks();
>          void CopyInputMeshToOutputMeshCells();
>          void CopyInputMeshToOutputMeshCellData();
>         
>         
>         The reason why a full CopyInputMeshToOutputMesh() method
>         can't be added directly up there is that in some cases the
>         types
>         of the InputMesh and OutputMesh are not compatible.
>         
>         In the LaplaceBeltrami filter, you may be in a case where
>         the types are compatible and therefore you can call the
>         methods listed above as building-blocks of what a
>         CopyInputMeshToOutputMesh() method could be.
>         
>         
>         Please give it a try at using the method above
>         and let us know if you find any problem.
>         
>         
>            Thanks
>         
>         
>             Luis
>         
>         
>         -----------------------------------------------
>         
>         On Fri, Nov 20, 2009 at 1:54 PM, Michael Bowers
>         <mbowers at cis.jhu.edu> wrote:
>         >
>         >
>         > Luis,
>         >
>         >
>         >
>         > I found CopyInputMeshToOutputMesh in
>         QuadEdgeMeshToQuadEdgeMeshFilter.  The
>         > Laplace Beltrami filter is MeshToMeshFilter, so I don’t
>         think I have the
>         > Copy function.  It seems like a useful thing to have in any
>         mesh-to-mesh
>         > filter.  Is there any possibility for pushing it into the
>         Base Class or do I
>         > need to implement it for the Laplace Beltrami filter?
>         >
>         >
>         >
>         > Thanks,
>         >
>         >
>         >
>         > Mike B.
>         >
>         >
>         >
>         >
>         
> 
> 
> 
> -- 
> Michel Audette, Ph.D. 
> R & D Engineer, 
> Kitware Inc.,
> Chapel Hill, N.C. 
>