[Imstk-developers] Line mesh connectivity
Milef, Nicholas Boris
milefn at rpi.edu
Fri Oct 27 10:49:45 EDT 2017
I'm talking about the line mesh, not the wireframe. I think you use it for camera nav to visualize the path (at least from the video), but I might be wrong.
________________________________
From: Alexis Girault [alexis.girault at kitware.com]
Sent: Friday, October 27, 2017 10:48 AM
To: Sreekanth Arikatla
Cc: Milef, Nicholas Boris; Hong Li; imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Line mesh connectivity
Nick: are you talking about surface mesh with wireframe representation? Because that is different from Line mesh.
Alexis Girault
R&D Engineer in Medical Computing
Kitware, Inc.
http://www.kitware.com<http://www.kitware.com/>
(919) 969-6990 x325<tel:(919)+969-6990+x325>
On Fri, Oct 27, 2017 at 10:46 AM, Sreekanth Arikatla <sreekanth.arikatla at kitware.com<mailto:sreekanth.arikatla at kitware.com>> wrote:
We have never used the line mesh but would need it though. It makes sense to fix it to use the connectivity information.
On Fri, Oct 27, 2017 at 10:43 AM, Alexis Girault <alexis.girault at kitware.com<mailto:alexis.girault at kitware.com>> wrote:
I don't think we have ever used the line mesh class here (correct me if I'm wrong Sreekanth). I think Hong wrote this.
@Hong: would you know if you were not using the connectivity information?
@Nick: whichever way, it seems we should just try to properly use it.
Alexis Girault
R&D Engineer in Medical Computing
Kitware, Inc.
http://www.kitware.com<http://www.kitware.com/>
(919) 969-6990 x325<tel:(919)+969-6990+x325>
On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
Right now, the LineMeshRenderDelegate behaves differently than the LineMesh geometry class implies. You can build a line mesh without connectivity information, and it still displays a valid line mesh. Meanwhile, the connectivity information seems to have no effect on the visual mesh itself.
________________________________
From: Alexis Girault [alexis.girault at kitware.com<mailto:alexis.girault at kitware.com>]
Sent: Thursday, October 26, 2017 9:23 AM
To: Sreekanth Arikatla
Cc: Milef, Nicholas Boris; imstk-developers at imstk.org<mailto:imstk-developers at imstk.org>
Subject: Re: [Imstk-developers] Line mesh connectivity
LineSource is a filter that uses two points to create a PolyLine. PolyLine is a 1D cell. If the filter does not do enough and you need to create a PolyLine that goes through multiple points, you might have to create your own filter (just a callback really) to update a PolyLine when you add points
On Thu, Oct 26, 2017, 09:19 Sreekanth Arikatla <sreekanth.arikatla at kitware.com<mailto:sreekanth.arikatla at kitware.com>> wrote:
vtkLineSource is being used inside the render delegate but I believe the right one is vtkPolyLine which is meant for a line passing through a bunch of points in the given order like in this example<https://www.vtk.org/Wiki/VTK/Examples/Cxx/GeometricObjects/PolyLine>.
On Wed, Oct 25, 2017 at 5:23 PM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
Is the line mesh connectivity used for anything? I'm looking in the line mesh render delegate for VTK, and the connectivity info doesn't appear to be used anywhere.
_______________________________________________
Imstk-developers mailing list
Imstk-developers at imstk.org<mailto:Imstk-developers at imstk.org>
http://public.kitware.com/mailman/listinfo/imstk-developers
--
Sreekanth Arikatla, Ph.D.,
Senior R&D Engineer,
Kitware, Inc.<http://www.kitware.com>, Carrboro, NC.
_______________________________________________
Imstk-developers mailing list
Imstk-developers at imstk.org<mailto:Imstk-developers at imstk.org>
http://public.kitware.com/mailman/listinfo/imstk-developers
--
Sreekanth Arikatla, Ph.D.,
Senior R&D Engineer,
Kitware, Inc.<http://www.kitware.com>, Carrboro, NC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171027/6246eb7f/attachment-0001.html>
More information about the Imstk-developers
mailing list