[Imstk-developers] Clearing surface mesh data on intialization

[Milef, Nicholas Boris]

For now, I can just put the seam computation before the clear. However, this will break if the vertex order changes or something like that. Basically, what I'm trying to say is that I would want users to know explicitly if they're messing up their data. A reinitialize function doesn't convey this imo.
________________________________
From: Imstk-developers [imstk-developers-bounces at imstk.org] on behalf of Milef, Nicholas Boris [milefn at rpi.edu]
Sent: Thursday, July 27, 2017 4:47 PM
To: Sreekanth Arikatla
Cc: imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Clearing surface mesh data on intialization

I guess where I'm stuck at is why we have an initialize function to begin with. I still can't think of a use-case where we can't either 1) make a new mesh or 2) modify the components of the old mesh.
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com]
Sent: Thursday, July 27, 2017 4:37 PM
To: Milef, Nicholas Boris
Cc: imstk-developers at imstk.org
Subject: Re: [Imstk-developers] Clearing surface mesh data on intialization

Hi Nick,
            If you want to preserve the normals, you can add normals to the Initialize function arg. If the normals are supplied, initialize clears the previous data before assigning.

On Thu, Jul 27, 2017 at 4:01 PM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
No, I don't. I need to preserve the original normals that ASSIMP imports because ASSIMP calculates the normals correctly. Otherwise, I can't identify the UV seams.

I can just do this computation in the SurfaceMeshRenderDelegate, but I'm not sure if the normals are used elsewhere after reinitializing the meshes. But isn't reinitializing a mesh dangerous in a multithreaded environment anyway?
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com<mailto:sreekanth.arikatla at kitware.com>]
Sent: Thursday, July 27, 2017 3:55 PM

To: Milef, Nicholas Boris
Cc: imstk-developers at imstk.org<mailto:imstk-developers at imstk.org>
Subject: Re: [Imstk-developers] Clearing surface mesh data on intialization

It could be used in some cases depending on the scenario. Do you plan to call this at every frame?


On Thu, Jul 27, 2017 at 3:53 PM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
Is that a useful use case though? Why not just make a new mesh?
________________________________
From: Sreekanth Arikatla [sreekanth.arikatla at kitware.com<mailto:sreekanth.arikatla at kitware.com>]
Sent: Thursday, July 27, 2017 3:52 PM
To: Milef, Nicholas Boris
Cc: imstk-developers at imstk.org<mailto:imstk-developers at imstk.org>
Subject: Re: [Imstk-developers] Clearing surface mesh data on intialization

Hi Nick,
            This is cleared in case one wants to reinitialize the mesh with a different data. Initialize should only be called at initilization or at runtime if the mesh data itself changes.

On Thu, Jul 27, 2017 at 3:31 PM, Milef, Nicholas Boris <milefn at rpi.edu<mailto:milefn at rpi.edu>> wrote:
I'm modifying the SurfaceMesh class currently, but why is all the data cleared on initialization? Is this necessary? I ask because I need this data to correct for the normals seams.

_______________________________________________
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/20170727/5f743da7/attachment.html>