From milefn at rpi.edu  Mon Oct  2 14:44:37 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Mon, 2 Oct 2017 18:44:37 +0000
Subject: [Imstk-developers] Deferred decals
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96AFCC1@ex14mb4.win.rpi.edu>

What tradeoffs do you all want for deferred decals? The main issue is which objects get affected by which decals (since a projection volume encompasses the target area). Deferred decals would be used for various markings such as burn marks, blood, or possibly just environmental details. You can think of them as a sticker.

Here is a decent overview of the technique and the problem with volume (please read if you're unfamiliar with this topic):
https://mtnphil.wordpress.com/2014/05/24/decals-deferred-rendering/

Option 1:
Add a material option to toggle decals on or off for a given mesh. This is the easiest implementation but also the most limited (meshes are either affected by all decals or none).

Option 2:
Add a mask for up to 8 types (layers) of decals. Each layer would be a property in the material class. You could can put the same type of decal (such as burn marks) on different layers to apply them to different meshes, but you are only limited to 8 layers total. This takes up 1 byte in the GBuffer. If we use two bytes, we can use up to 16 layers.

Option 3:
Add a material ID for each mesh in the simulator. Each decal would be assigned to one mesh. This would allow up to 256 unique meshes but unlimited types of decals. This takes up 1 byte in the GBuffer. If we use 2 bytes, then we can use up to 65k unique meshes. The drawback is that there can be a large amount of drawing/overdraw here (since decals must be drawn multiple times for each compatible material in the scene), which is expensive on both the CPU and GPU side.

Personally, I'm leaning towards Option 2, but I was wondering what you all thought.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171002/01d96e98/attachment.html>

From sreekanth.arikatla at kitware.com  Tue Oct  3 10:34:01 2017
From: sreekanth.arikatla at kitware.com (Sreekanth Arikatla)
Date: Tue, 3 Oct 2017 10:34:01 -0400
Subject: [Imstk-developers] Deferred decals
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96AFCC1@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96AFCC1@ex14mb4.win.rpi.edu>
Message-ID: <CAJFrbFL0bbijJ3-9FAfEZZwR+0uOa7xCpQaZ_jEAGOLQ6iup=Q@mail.gmail.com>

Hi Nick,
            Read the blog, option 2 seems fine to me. Can deferred decals
be used for the case of cuts with blood that evolves between frames?

On Mon, Oct 2, 2017 at 2:44 PM, Milef, Nicholas Boris <milefn at rpi.edu>
wrote:

> What tradeoffs do you all want for deferred decals? The main issue is
> which objects get affected by which decals (since a projection volume
> encompasses the target area). Deferred decals would be used for various
> markings such as burn marks, blood, or possibly just environmental details.
> You can think of them as a sticker.
>
> Here is a decent overview of the technique and the problem with volume
> (please read if you're unfamiliar with this topic):
> https://mtnphil.wordpress.com/2014/05/24/decals-deferred-rendering/
>
> Option 1:
> Add a material option to toggle decals on or off for a given mesh. This is
> the easiest implementation but also the most limited (meshes are either
> affected by all decals or none).
>
> Option 2:
> Add a mask for up to 8 types (layers) of decals. Each layer would be a
> property in the material class. You could can put the same type of decal
> (such as burn marks) on different layers to apply them to different meshes,
> but you are only limited to 8 layers total. This takes up 1 byte in the
> GBuffer. If we use two bytes, we can use up to 16 layers.
>
> Option 3:
> Add a material ID for each mesh in the simulator. Each decal would be
> assigned to one mesh. This would allow up to 256 unique meshes but
> unlimited types of decals. This takes up 1 byte in the GBuffer. If we use 2
> bytes, then we can use up to 65k unique meshes. The drawback is that there
> can be a large amount of drawing/overdraw here (since decals must be drawn
> multiple times for each compatible material in the scene), which is
> expensive on both the CPU and GPU side.
>
> Personally, I'm leaning towards Option 2, but I was wondering what you all
> thought.
>
> _______________________________________________
> Imstk-developers mailing list
> 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/20171003/6b505818/attachment.html>

From milefn at rpi.edu  Tue Oct  3 12:52:34 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Tue, 3 Oct 2017 16:52:34 +0000
Subject: [Imstk-developers] Deferred decals
In-Reply-To: <CAJFrbFL0bbijJ3-9FAfEZZwR+0uOa7xCpQaZ_jEAGOLQ6iup=Q@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96AFCC1@ex14mb4.win.rpi.edu>,
 <CAJFrbFL0bbijJ3-9FAfEZZwR+0uOa7xCpQaZ_jEAGOLQ6iup=Q@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96AFD6A@ex14mb4.win.rpi.edu>

Yes, that is a possible use case. In that case, you would probably create a bunch of decals to simulate a trail of blood. You would have a decal pool for each layer, so you could have hundreds or thousands of decals per layer. You could have them at different scales as well (so each decal can grow). I might add functionality to have decal sheets so that each layer can have a number of variations, but this could mess up mipmaps slightly.

If you wanted something more organic, you would need to do what Tansel did in his blood shaders, but I don't want to implement that until the material editor is more-or-less complete.
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com]
Sent: Tuesday, October 03, 2017 10:34 AM
To: Milef, Nicholas Boris
Cc: imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Deferred decals

Hi Nick,
            Read the blog, option 2 seems fine to me. Can deferred decals be used for the case of cuts with blood that evolves between frames?

On Mon, Oct 2, 2017 at 2:44 PM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
What tradeoffs do you all want for deferred decals? The main issue is which objects get affected by which decals (since a projection volume encompasses the target area). Deferred decals would be used for various markings such as burn marks, blood, or possibly just environmental details. You can think of them as a sticker.

Here is a decent overview of the technique and the problem with volume (please read if you're unfamiliar with this topic):
https://mtnphil.wordpress.com/2014/05/24/decals-deferred-rendering/

Option 1:
Add a material option to toggle decals on or off for a given mesh. This is the easiest implementation but also the most limited (meshes are either affected by all decals or none).

Option 2:
Add a mask for up to 8 types (layers) of decals. Each layer would be a property in the material class. You could can put the same type of decal (such as burn marks) on different layers to apply them to different meshes, but you are only limited to 8 layers total. This takes up 1 byte in the GBuffer. If we use two bytes, we can use up to 16 layers.

Option 3:
Add a material ID for each mesh in the simulator. Each decal would be assigned to one mesh. This would allow up to 256 unique meshes but unlimited types of decals. This takes up 1 byte in the GBuffer. If we use 2 bytes, then we can use up to 65k unique meshes. The drawback is that there can be a large amount of drawing/overdraw here (since decals must be drawn multiple times for each compatible material in the scene), which is expensive on both the CPU and GPU side.

Personally, I'm leaning towards Option 2, but I was wondering what you all thought.

_______________________________________________
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/20171003/86cb5a69/attachment.html>

From milefn at rpi.edu  Wed Oct 25 17:23:04 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Wed, 25 Oct 2017 21:23:04 +0000
Subject: [Imstk-developers] Line mesh connectivity
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171025/0c846616/attachment.html>

From sreekanth.arikatla at kitware.com  Thu Oct 26 09:18:59 2017
From: sreekanth.arikatla at kitware.com (Sreekanth Arikatla)
Date: Thu, 26 Oct 2017 09:18:59 -0400
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
Message-ID: <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>

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>
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
> 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/20171026/9cf677ba/attachment.html>

From alexis.girault at kitware.com  Thu Oct 26 09:23:43 2017
From: alexis.girault at kitware.com (Alexis Girault)
Date: Thu, 26 Oct 2017 13:23:43 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
Message-ID: <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>

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> 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>
> 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
>> 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
> http://public.kitware.com/mailman/listinfo/imstk-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171026/fffd0c4e/attachment.html>

From milefn at rpi.edu  Fri Oct 27 10:17:08 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Fri, 27 Oct 2017 14:17:08 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>,
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>

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]
Sent: Thursday, October 26, 2017 9:23 AM
To: Sreekanth Arikatla
Cc: Milef, Nicholas Boris; 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171027/d38d7dbd/attachment.html>

From alexis.girault at kitware.com  Fri Oct 27 10:43:41 2017
From: alexis.girault at kitware.com (Alexis Girault)
Date: Fri, 27 Oct 2017 10:43:41 -0400
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
Message-ID: <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>

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
(919) 969-6990 x325

On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <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]
> *Sent:* Thursday, October 26, 2017 9:23 AM
> *To:* Sreekanth Arikatla
> *Cc:* Milef, Nicholas Boris; 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> 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>
>> 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
>>> 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
>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171027/44ab9eef/attachment.html>

From milefn at rpi.edu  Fri Oct 27 10:46:21 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Fri, 27 Oct 2017 14:46:21 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>,
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96B0EA4@ex14mb4.win.rpi.edu>

I'ts useful for debugging. Where was that discussion? I don't understand the context.
________________________________
From: Alexis Girault [alexis.girault at kitware.com]
Sent: Friday, October 27, 2017 10:43 AM
To: Milef, Nicholas Boris; Hong Li
Cc: Sreekanth Arikatla; imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Line mesh connectivity

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171027/9f869b2c/attachment-0001.html>

From sreekanth.arikatla at kitware.com  Fri Oct 27 10:46:43 2017
From: sreekanth.arikatla at kitware.com (Sreekanth Arikatla)
Date: Fri, 27 Oct 2017 10:46:43 -0400
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
Message-ID: <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>

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
> 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
> (919) 969-6990 x325
>
> On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <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]
>> *Sent:* Thursday, October 26, 2017 9:23 AM
>> *To:* Sreekanth Arikatla
>> *Cc:* Milef, Nicholas Boris; 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> 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>
>>> 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
>>>> 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
>>> 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/30785f01/attachment.html>

From alexis.girault at kitware.com  Fri Oct 27 10:48:23 2017
From: alexis.girault at kitware.com (Alexis Girault)
Date: Fri, 27 Oct 2017 10:48:23 -0400
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
 <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>
Message-ID: <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>

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
(919) 969-6990 x325

On Fri, Oct 27, 2017 at 10:46 AM, Sreekanth Arikatla <
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> 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
>> (919) 969-6990 x325
>>
>> On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <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]
>>> *Sent:* Thursday, October 26, 2017 9:23 AM
>>> *To:* Sreekanth Arikatla
>>> *Cc:* Milef, Nicholas Boris; 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> 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>
>>>> 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
>>>>> 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
>>>> 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/d2e529de/attachment.html>

From milefn at rpi.edu  Fri Oct 27 10:49:45 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Fri, 27 Oct 2017 14:49:45 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
 <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>,
 <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96B0EC6@ex14mb4.win.rpi.edu>

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>

From sreekanth.arikatla at kitware.com  Fri Oct 27 11:12:27 2017
From: sreekanth.arikatla at kitware.com (Sreekanth Arikatla)
Date: Fri, 27 Oct 2017 11:12:27 -0400
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96B0EC6@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
 <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>
 <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0EC6@ex14mb4.win.rpi.edu>
Message-ID: <CAJFrbFJ4pyF7pKwS6tAe3jXbBP-n2BMjt4_zyFKB1YG4vS8YUA@mail.gmail.com>

In cameraNavigation we don't use the line mesh from imstk but rather
directly use vtk polydata.


On Fri, Oct 27, 2017 at 10:49 AM, Milef, Nicholas Boris <milefn at rpi.edu>
wrote:

> 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
> (919) 969-6990 x325
>
> On Fri, Oct 27, 2017 at 10:46 AM, Sreekanth Arikatla <
> 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> 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
>>> (919) 969-6990 x325
>>>
>>> On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <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]
>>>> *Sent:* Thursday, October 26, 2017 9:23 AM
>>>> *To:* Sreekanth Arikatla
>>>> *Cc:* Milef, Nicholas Boris; 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> 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
>>>>> > 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
>>>>>> 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
>>>>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>>>>
>>>>
>>>
>>
>>
>> --
>> Sreekanth Arikatla, Ph.D.,
>> Senior R&D Engineer,
>> Kitware, Inc. <http://www.kitware.com>, Carrboro, NC.
>>
>>
>


-- 
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/f064ece3/attachment.html>

From milefn at rpi.edu  Fri Oct 27 11:46:47 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Fri, 27 Oct 2017 15:46:47 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAJFrbFJ4pyF7pKwS6tAe3jXbBP-n2BMjt4_zyFKB1YG4vS8YUA@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
 <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>
 <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0EC6@ex14mb4.win.rpi.edu>,
 <CAJFrbFJ4pyF7pKwS6tAe3jXbBP-n2BMjt4_zyFKB1YG4vS8YUA@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96B0EE5@ex14mb4.win.rpi.edu>

Is the polydata made up of lines? Or is it wireframe triangles?
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com]
Sent: Friday, October 27, 2017 11:12 AM
To: Milef, Nicholas Boris
Cc: Alexis Girault; Hong Li; imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Line mesh connectivity

In cameraNavigation we don't use the line mesh from imstk but rather directly use vtk polydata.


On Fri, Oct 27, 2017 at 10:49 AM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
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<mailto: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<mailto: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.





--
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/93944d6e/attachment-0001.html>

From sreekanth.arikatla at kitware.com  Fri Oct 27 11:50:36 2017
From: sreekanth.arikatla at kitware.com (Sreekanth Arikatla)
Date: Fri, 27 Oct 2017 11:50:36 -0400
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96B0EE5@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
 <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>
 <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0EC6@ex14mb4.win.rpi.edu>
 <CAJFrbFJ4pyF7pKwS6tAe3jXbBP-n2BMjt4_zyFKB1YG4vS8YUA@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0EE5@ex14mb4.win.rpi.edu>
Message-ID: <CAJFrbF+YJOGJG_0onu0P4TEz8=MCUjmp+oYfR==TJ-B5m3UbPA@mail.gmail.com>

Yes its made of lines.


On Fri, Oct 27, 2017 at 11:46 AM, Milef, Nicholas Boris <milefn at rpi.edu>
wrote:

> Is the polydata made up of lines? Or is it wireframe triangles?
> ------------------------------
> *From:* Sreekanth Arikatla [sreekanth.arikatla at kitware.com]
> *Sent:* Friday, October 27, 2017 11:12 AM
> *To:* Milef, Nicholas Boris
> *Cc:* Alexis Girault; Hong Li; imstk-developers at imstk.org
>
> *Subject:* Re: [Imstk-developers] Line mesh connectivity
>
> In cameraNavigation we don't use the line mesh from imstk but rather
> directly use vtk polydata.
>
>
> On Fri, Oct 27, 2017 at 10:49 AM, Milef, Nicholas Boris <milefn at rpi.edu>
> wrote:
>
>> 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
>> (919) 969-6990 x325
>>
>> On Fri, Oct 27, 2017 at 10:46 AM, Sreekanth Arikatla <
>> 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> 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
>>>> (919) 969-6990 x325
>>>>
>>>> On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <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]
>>>>> *Sent:* Thursday, October 26, 2017 9:23 AM
>>>>> *To:* Sreekanth Arikatla
>>>>> *Cc:* Milef, Nicholas Boris; 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> 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> 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
>>>>>>> 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
>>>>>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Sreekanth Arikatla, Ph.D.,
>>> Senior R&D Engineer,
>>> Kitware, Inc. <http://www.kitware.com>, Carrboro, NC.
>>>
>>>
>>
>
>
> --
> Sreekanth Arikatla, Ph.D.,
> Senior R&D Engineer,
> Kitware, Inc. <http://www.kitware.com>, Carrboro, NC.
>
>


-- 
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/7331b727/attachment.html>

From milefn at rpi.edu  Fri Oct 27 12:18:11 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Fri, 27 Oct 2017 16:18:11 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAJFrbF+YJOGJG_0onu0P4TEz8=MCUjmp+oYfR==TJ-B5m3UbPA@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
 <CAJFrbF+0EN1uafJBWUWUGabZR1NBbsDU3yX0K3R6zLtf8NqahQ@mail.gmail.com>
 <CAG1Y6mAkrSTmq1b1KpPO8tWLvUXa1F7phm70K=55OzRqByYx4w@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0EC6@ex14mb4.win.rpi.edu>
 <CAJFrbFJ4pyF7pKwS6tAe3jXbBP-n2BMjt4_zyFKB1YG4vS8YUA@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0EE5@ex14mb4.win.rpi.edu>,
 <CAJFrbF+YJOGJG_0onu0P4TEz8=MCUjmp+oYfR==TJ-B5m3UbPA@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96B0F08@ex14mb4.win.rpi.edu>

Ok, I'll have an MR in a few hours for this. It'll work with the load factor as well and have options for colored lines.

@Alexis, I think I caused some confusion. I misinterpreted your @Nick a few messages back to being a quote I made for some reason.
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com]
Sent: Friday, October 27, 2017 11:50 AM
To: Milef, Nicholas Boris
Cc: Alexis Girault; Hong Li; imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Line mesh connectivity

Yes its made of lines.


On Fri, Oct 27, 2017 at 11:46 AM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
Is the polydata made up of lines? Or is it wireframe triangles?
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com<mailto:sreekanth.arikatla at kitware.com>]
Sent: Friday, October 27, 2017 11:12 AM
To: Milef, Nicholas Boris
Cc: Alexis Girault; Hong Li; imstk-developers at imstk.org<mailto:imstk-developers at imstk.org>

Subject: Re: [Imstk-developers] Line mesh connectivity

In cameraNavigation we don't use the line mesh from imstk but rather directly use vtk polydata.


On Fri, Oct 27, 2017 at 10:49 AM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
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<mailto: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<mailto: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.





--
Sreekanth Arikatla, Ph.D.,
Senior R&D Engineer,
Kitware, Inc.<http://www.kitware.com>, Carrboro, NC.




--
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/be31f1c3/attachment.html>

From hongli03129 at gmail.com  Fri Oct 27 13:25:07 2017
From: hongli03129 at gmail.com (Hong Li)
Date: Fri, 27 Oct 2017 17:25:07 +0000
Subject: [Imstk-developers] Line mesh connectivity
In-Reply-To: <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96B0D45@ex14mb4.win.rpi.edu>
 <CAJFrbFLz+Fd9YfzCkORjK85TMW+=5KW_cLkVsZY+cZmz59==DA@mail.gmail.com>
 <CAG1Y6mDN0MiQeDYtXXonLnHLticbMBNmS-pBno8wgcVb_QPZnw@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96B0E7B@ex14mb4.win.rpi.edu>
 <CAG1Y6mDen4xH+PZ5Ocu-PacbaHGQgs8QBG3EnwXRTkoK0a0r0Q@mail.gmail.com>
Message-ID: <CAMB8zNXeqfS=eEztpjv1MKMRBqtuS2Lw2dgkXf+A4MOEsirRSg@mail.gmail.com>

Hi Alexis,
The connectivity info of linemesh was used for collision detection and
handing in PBD, for Line-Line collision pairs.

On Fri, Oct 27, 2017 at 10:43 AM Alexis Girault <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
> (919) 969-6990 x325
>
> On Fri, Oct 27, 2017 at 10:17 AM, Milef, Nicholas Boris <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]
>> *Sent:* Thursday, October 26, 2017 9:23 AM
>> *To:* Sreekanth Arikatla
>> *Cc:* Milef, Nicholas Boris; 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> 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>
>>> 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
>>>> 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
>>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20171027/f8960978/attachment-0001.html>