From milefn at rpi.edu  Wed May 10 17:37:57 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Wed, 10 May 2017 21:37:57 +0000
Subject: [Imstk-developers] Updating VTK version rules
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96A7EFD@ex14mb4.win.rpi.edu>

I need to update VTK to at least:
fd8bfb599d9fb78cd6589363bd717d3f1007d22b

because of VBO related features. What's the general rule to this, should I update to the most recent version/commit of VTK or just this commit?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170510/3ffb2c4b/attachment.html>

From dzenan.zukic at kitware.com  Wed May 10 17:55:14 2017
From: dzenan.zukic at kitware.com (Dzenan Zukic)
Date: Wed, 10 May 2017 17:55:14 -0400
Subject: [Imstk-developers] Updating VTK version rules
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96A7EFD@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96A7EFD@ex14mb4.win.rpi.edu>
Message-ID: <CAPmoeGZ=5D_xXaB79F2JLQqL4xM5-zg9irA7RhATc2o-9vL4bw@mail.gmail.com>

It is best to update to the most recent release, unless that is not new
enough. In that case it is probably best to update to master.

D?enan Zuki?, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)

On Wed, May 10, 2017 at 5:37 PM, Milef, Nicholas Boris <milefn at rpi.edu>
wrote:

> I need to update VTK to at least:
> fd8bfb599d9fb78cd6589363bd717d3f1007d22b
>
> because of VBO related features. What's the general rule to this, should I
> update to the most recent version/commit of VTK or just this commit?
>
> _______________________________________________
> 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/20170510/ae2c26a6/attachment.html>

From alexis.girault at kitware.com  Wed May 10 17:57:00 2017
From: alexis.girault at kitware.com (Alexis Girault)
Date: Wed, 10 May 2017 21:57:00 +0000
Subject: [Imstk-developers] Updating VTK version rules
In-Reply-To: <CAPmoeGZ=5D_xXaB79F2JLQqL4xM5-zg9irA7RhATc2o-9vL4bw@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96A7EFD@ex14mb4.win.rpi.edu>
 <CAPmoeGZ=5D_xXaB79F2JLQqL4xM5-zg9irA7RhATc2o-9vL4bw@mail.gmail.com>
Message-ID: <CAG1Y6mCcnnCarOy1T2rq7PChFfQHqB4BkasUhWBxVQDbeXKoxA@mail.gmail.com>

I'd agree with Dzenan, unless there is a stable release previous to latest
master. Also, there can be regressions sometimes, so we just have to make
sure that the rest works.

On Wed, May 10, 2017, 17:55 Dzenan Zukic <dzenan.zukic at kitware.com> wrote:

> It is best to update to the most recent release, unless that is not new
> enough. In that case it is probably best to update to master.
>
> D?enan Zuki?, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)
>
> On Wed, May 10, 2017 at 5:37 PM, Milef, Nicholas Boris <milefn at rpi.edu>
> wrote:
>
>> I need to update VTK to at least:
>> fd8bfb599d9fb78cd6589363bd717d3f1007d22b
>>
>> because of VBO related features. What's the general rule to this, should
>> I update to the most recent version/commit of VTK or just this commit?
>>
>> _______________________________________________
>> Imstk-developers mailing list
>> Imstk-developers at imstk.org
>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>
>>
> _______________________________________________
> 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/20170510/f4b18bd0/attachment.html>

From milefn at rpi.edu  Thu May 11 12:04:01 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Thu, 11 May 2017 16:04:01 +0000
Subject: [Imstk-developers] Updating VTK version rules
In-Reply-To: <CAG1Y6mCcnnCarOy1T2rq7PChFfQHqB4BkasUhWBxVQDbeXKoxA@mail.gmail.com>
References: <C745C1E748CE104AA373B656E0EF5E30E96A7EFD@ex14mb4.win.rpi.edu>
 <CAPmoeGZ=5D_xXaB79F2JLQqL4xM5-zg9irA7RhATc2o-9vL4bw@mail.gmail.com>,
 <CAG1Y6mCcnnCarOy1T2rq7PChFfQHqB4BkasUhWBxVQDbeXKoxA@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96A7F93@ex14mb4.win.rpi.edu>

I looked at version 7.1.1 (the most recent version?), and it doesn't have the changes that I need. How should I proceed?

Alternatively, I can also make my own VBO class since it's pretty trivial, and we could stick with the current version. I'm fine with either option.
________________________________
From: Alexis Girault [alexis.girault at kitware.com]
Sent: Wednesday, May 10, 2017 5:57 PM
To: Dzenan Zukic; Milef, Nicholas Boris
Cc: imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Updating VTK version rules


I'd agree with Dzenan, unless there is a stable release previous to latest master. Also, there can be regressions sometimes, so we just have to make sure that the rest works.

On Wed, May 10, 2017, 17:55 Dzenan Zukic <dzenan.zukic at kitware.com<mailto:dzenan.zukic at kitware.com>> wrote:
It is best to update to the most recent release, unless that is not new enough. In that case it is probably best to update to master.

D?enan Zuki?, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)

On Wed, May 10, 2017 at 5:37 PM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
I need to update VTK to at least:
fd8bfb599d9fb78cd6589363bd717d3f1007d22b

because of VBO related features. What's the general rule to this, should I update to the most recent version/commit of VTK or just this commit?

_______________________________________________
Imstk-developers mailing list
Imstk-developers at imstk.org<mailto:Imstk-developers at imstk.org>
http://public.kitware.com/mailman/listinfo/imstk-developers


_______________________________________________
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/20170511/3ce77834/attachment.html>

From alexis.girault at kitware.com  Thu May 11 13:53:18 2017
From: alexis.girault at kitware.com (Alexis Girault)
Date: Thu, 11 May 2017 17:53:18 +0000
Subject: [Imstk-developers] Updating VTK version rules
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96A7F93@ex14mb4.win.rpi.edu>
References: <C745C1E748CE104AA373B656E0EF5E30E96A7EFD@ex14mb4.win.rpi.edu>
 <CAPmoeGZ=5D_xXaB79F2JLQqL4xM5-zg9irA7RhATc2o-9vL4bw@mail.gmail.com>
 <CAG1Y6mCcnnCarOy1T2rq7PChFfQHqB4BkasUhWBxVQDbeXKoxA@mail.gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96A7F93@ex14mb4.win.rpi.edu>
Message-ID: <CAG1Y6mD6RwyzT3OGRanT21dG6iYhUVonQ86A9vCJeNvQ03jVEg@mail.gmail.com>

If what you need is in latest master, let's have it up to date then.
Thanks!

On Thu, May 11, 2017, 12:04 Milef, Nicholas Boris <milefn at rpi.edu> wrote:

> I looked at version 7.1.1 (the most recent version?), and it doesn't have
> the changes that I need. How should I proceed?
>
> Alternatively, I can also make my own VBO class since it's pretty trivial,
> and we could stick with the current version. I'm fine with either option.
> ------------------------------
> *From:* Alexis Girault [alexis.girault at kitware.com]
> *Sent:* Wednesday, May 10, 2017 5:57 PM
> *To:* Dzenan Zukic; Milef, Nicholas Boris
> *Cc:* imstk-developers at imstk.org
> *Subject:* Re: [Imstk-developers] Updating VTK version rules
>
> I'd agree with Dzenan, unless there is a stable release previous to latest
> master. Also, there can be regressions sometimes, so we just have to make
> sure that the rest works.
>
> On Wed, May 10, 2017, 17:55 Dzenan Zukic <dzenan.zukic at kitware.com> wrote:
>
>> It is best to update to the most recent release, unless that is not new
>> enough. In that case it is probably best to update to master.
>>
>> D?enan Zuki?, PhD, Senior R&D Engineer, Kitware (Carrboro, N.C.)
>>
>> On Wed, May 10, 2017 at 5:37 PM, Milef, Nicholas Boris <milefn at rpi.edu>
>> wrote:
>>
>>> I need to update VTK to at least:
>>> fd8bfb599d9fb78cd6589363bd717d3f1007d22b
>>>
>>> because of VBO related features. What's the general rule to this, should
>>> I update to the most recent version/commit of VTK or just this commit?
>>>
>>> _______________________________________________
>>> Imstk-developers mailing list
>>> Imstk-developers at imstk.org
>>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>>
>>>
>> _______________________________________________
>> 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/20170511/db5e84fb/attachment.html>

From unihui at gmail.com  Tue May 16 15:54:52 2017
From: unihui at gmail.com (Zhaohui Xia)
Date: Tue, 16 May 2017 15:54:52 -0400
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK
Message-ID: <002b01d2ce7e$48d0f2a0$da72d7e0$@gmail.com>

Hi,

Can we add the functionality in iMSTK for supporting rendering mesh with
wireframe mode? It will be helpful for debugging.

Best Regards,

Zhaohui

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170516/c1811e8f/attachment.html>

From milefn at rpi.edu  Tue May 16 16:04:19 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Tue, 16 May 2017 20:04:19 +0000
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK
In-Reply-To: <002b01d2ce7e$48d0f2a0$da72d7e0$@gmail.com>
References: <002b01d2ce7e$48d0f2a0$da72d7e0$@gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96A931A@ex14mb4.win.rpi.edu>

Hi Zhaohui,

You should do this with your material:
renderMaterial->wireframeOn(RenderMaterial::DisplayMode::WIREFRAME);

Thanks,
Nick

Software Engineer
Center for Modeling, Simulation, & Imaging in Medicine
Rensselaer Polytechnic Institute
milefn at rpi.edu
________________________________
From: Imstk-developers [imstk-developers-bounces at imstk.org] on behalf of Zhaohui Xia [unihui at gmail.com]
Sent: Tuesday, May 16, 2017 3:54 PM
To: imstk-developers at imstk.org
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK

Hi,
Can we add the functionality in iMSTK for supporting rendering mesh with wireframe mode? It will be helpful for debugging.
Best Regards,
Zhaohui
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170516/cb100864/attachment.html>

From unihui at gmail.com  Tue May 16 16:10:42 2017
From: unihui at gmail.com (Zhaohui Xia)
Date: Tue, 16 May 2017 16:10:42 -0400
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK
In-Reply-To: <C745C1E748CE104AA373B656E0EF5E30E96A931A@ex14mb4.win.rpi.edu>
References: <002b01d2ce7e$48d0f2a0$da72d7e0$@gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96A931A@ex14mb4.win.rpi.edu>
Message-ID: <003401d2ce80$7f77d060$7e677120$@gmail.com>

Thanks. But I cannot use the that version as we talked before.

 

From: Milef, Nicholas Boris [mailto:milefn at rpi.edu] 
Sent: 2017?5?16? 16:04
To: Zhaohui Xia <unihui at gmail.com>; imstk-developers at imstk.org
Subject: RE: [Imstk-developers] rendering mesh with wire frame mode in iMSTK

 

Hi Zhaohui, 

 

You should do this with your material:

renderMaterial->wireframeOn(RenderMaterial::DisplayMode::WIREFRAME);

 

Thanks,

Nick

 

Software Engineer 

Center for Modeling, Simulation, & Imaging in Medicine

Rensselaer Polytechnic Institute

milefn at rpi.edu <mailto:milefn at rpi.edu> 

  _____  

From: Imstk-developers [imstk-developers-bounces at imstk.org] on behalf of
Zhaohui Xia [unihui at gmail.com]
Sent: Tuesday, May 16, 2017 3:54 PM
To: imstk-developers at imstk.org <mailto:imstk-developers at imstk.org> 
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK

Hi,

Can we add the functionality in iMSTK for supporting rendering mesh with
wireframe mode? It will be helpful for debugging.

Best Regards,

Zhaohui

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

From alexis.girault at kitware.com  Tue May 16 16:16:57 2017
From: alexis.girault at kitware.com (Alexis Girault)
Date: Tue, 16 May 2017 16:16:57 -0400
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK
In-Reply-To: <003401d2ce80$7f77d060$7e677120$@gmail.com>
References: <002b01d2ce7e$48d0f2a0$da72d7e0$@gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96A931A@ex14mb4.win.rpi.edu>
 <003401d2ce80$7f77d060$7e677120$@gmail.com>
Message-ID: <CAG1Y6mDsnNhJ69Vbi9X-LzggA9db=wyydVSf9n=oW9ESz1d+ow@mail.gmail.com>

>
> You should do this with your material:
> renderMaterial->wireframeOn(RenderMaterial::DisplayMode::WIREFRAME);


That's the way, just using RenderMaterial::setDisplayMode()
<https://gitlab.kitware.com/iMSTK/iMSTK/blob/838ff72/Base/Materials/imstkRenderMaterial.h#L39-56>
and not RenderMaterial::wireframeOn() which doesn't exist. You could also
use DisplayMode::WIREFRAME_SURFACE as an argument if you want to see both
surface and wireframe.

Thanks. But I cannot use the that version as we talked before.
>

What do you mean by that? Do you encounter issues with the latest version
which were not in previous versions of iMSTK?


Alexis Girault
R&D Engineer in Medical Computing
Kitware, Inc.

http://www.kitware.com
(919) 969-6990 x325

On Tue, May 16, 2017 at 4:10 PM, Zhaohui Xia <unihui at gmail.com> wrote:

> Thanks. But I cannot use the that version as we talked before.
>
>
>
> *From:* Milef, Nicholas Boris [mailto:milefn at rpi.edu]
> *Sent:* 2017?5?16? 16:04
> *To:* Zhaohui Xia <unihui at gmail.com>; imstk-developers at imstk.org
> *Subject:* RE: [Imstk-developers] rendering mesh with wire frame mode in
> iMSTK
>
>
>
> Hi Zhaohui,
>
>
>
> You should do this with your material:
>
> renderMaterial->wireframeOn(RenderMaterial::DisplayMode::WIREFRAME);
>
>
>
> Thanks,
>
> Nick
>
>
>
> Software Engineer
>
> Center for Modeling, Simulation, & Imaging in Medicine
>
> Rensselaer Polytechnic Institute
>
> milefn at rpi.edu
> ------------------------------
>
> *From:* Imstk-developers [imstk-developers-bounces at imstk.org] on behalf
> of Zhaohui Xia [unihui at gmail.com]
> *Sent:* Tuesday, May 16, 2017 3:54 PM
> *To:* imstk-developers at imstk.org
> *Subject:* [Imstk-developers] rendering mesh with wire frame mode in iMSTK
>
> Hi,
>
> Can we add the functionality in iMSTK for supporting rendering mesh with
> wireframe mode? It will be helpful for debugging.
>
> Best Regards,
>
> Zhaohui
>
> _______________________________________________
> 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/20170516/d737b1f6/attachment-0001.html>

From milefn at rpi.edu  Tue May 16 17:07:45 2017
From: milefn at rpi.edu (Milef, Nicholas Boris)
Date: Tue, 16 May 2017 21:07:45 +0000
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK
In-Reply-To: <CAG1Y6mDsnNhJ69Vbi9X-LzggA9db=wyydVSf9n=oW9ESz1d+ow@mail.gmail.com>
References: <002b01d2ce7e$48d0f2a0$da72d7e0$@gmail.com>
 <C745C1E748CE104AA373B656E0EF5E30E96A931A@ex14mb4.win.rpi.edu>
 <003401d2ce80$7f77d060$7e677120$@gmail.com>,
 <CAG1Y6mDsnNhJ69Vbi9X-LzggA9db=wyydVSf9n=oW9ESz1d+ow@mail.gmail.com>
Message-ID: <C745C1E748CE104AA373B656E0EF5E30E96A933B@ex14mb4.win.rpi.edu>

@Alexis, Thanks for the correction. I had an earlier branch that had a wireframeOn() function. We solved this issue by updating to the latest version of my fork.

@Zhaohui, I currently don't support WIREFRAME_SURFACE or POINTS on my Vulkan branch, just SURFACE and WIREFRAME for now.
________________________________
From: Alexis Girault [alexis.girault at kitware.com]
Sent: Tuesday, May 16, 2017 4:16 PM
To: Zhaohui Xia
Cc: Milef, Nicholas Boris; imstk-developers at imstk.org
Subject: Re: [Imstk-developers] rendering mesh with wire frame mode in iMSTK

You should do this with your material:
renderMaterial->wireframeOn(RenderMaterial::DisplayMode::WIREFRAME);

That's the way, just using RenderMaterial::setDisplayMode()<https://gitlab.kitware.com/iMSTK/iMSTK/blob/838ff72/Base/Materials/imstkRenderMaterial.h#L39-56> and not RenderMaterial::wireframeOn() which doesn't exist. You could also use DisplayMode::WIREFRAME_SURFACE as an argument if you want to see both surface and wireframe.

Thanks. But I cannot use the that version as we talked before.

What do you mean by that? Do you encounter issues with the latest version which were not in previous versions of iMSTK?


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 Tue, May 16, 2017 at 4:10 PM, Zhaohui Xia <unihui at gmail.com<mailto:unihui at gmail.com>> wrote:
Thanks. But I cannot use the that version as we talked before.

From: Milef, Nicholas Boris [mailto:milefn at rpi.edu<mailto:milefn at rpi.edu>]
Sent: 2017?5?16? 16:04
To: Zhaohui Xia <unihui at gmail.com<mailto:unihui at gmail.com>>; imstk-developers at imstk.org<mailto:imstk-developers at imstk.org>
Subject: RE: [Imstk-developers] rendering mesh with wire frame mode in iMSTK

Hi Zhaohui,

You should do this with your material:
renderMaterial->wireframeOn(RenderMaterial::DisplayMode::WIREFRAME);

Thanks,
Nick

Software Engineer
Center for Modeling, Simulation, & Imaging in Medicine
Rensselaer Polytechnic Institute
milefn at rpi.edu<mailto:milefn at rpi.edu>
________________________________
From: Imstk-developers [imstk-developers-bounces at imstk.org<mailto:imstk-developers-bounces at imstk.org>] on behalf of Zhaohui Xia [unihui at gmail.com<mailto:unihui at gmail.com>]
Sent: Tuesday, May 16, 2017 3:54 PM
To: imstk-developers at imstk.org<mailto:imstk-developers at imstk.org>
Subject: [Imstk-developers] rendering mesh with wire frame mode in iMSTK
Hi,
Can we add the functionality in iMSTK for supporting rendering mesh with wireframe mode? It will be helpful for debugging.
Best Regards,
Zhaohui

_______________________________________________
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/20170516/ac46a3f0/attachment.html>