Thoughts on possible next steps:
[ ] 6 (?). Independent Unstructured Grid to PolyData WebAssembly support, vtk.js Unstructured Grid support, Unstructured Grid IO WebAssembly
I think it might be a good test for vtk-emscripten - IO and conversion class.
Yes! :space_invader: :sparkler: :sparkling_heart:
Starting on this.
Inserted 4.b) - ITK SpatialObject to VTK PolyData :-D
It might be better if spatial objects are "mapped" to VTK implicit
functions, they are nearly the same thing. Then in VTK, there are tools for
generating surfaces (ie polydata), selecting and extracting data etc with
implicit functions. But depending on workflow there are probably a couple
of different paths to take....
On Thu, Feb 7, 2019 at 2:13 PM Matt McCormick notifications@github.com
wrote:
Yes! 👾 🎇 💖
Starting on this.
Inserted 4.b) - ITK SpatialObject to VTK PolyData :-D
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/vtk-js/issues/976#issuecomment-461558218, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAMMcsmA4AseshqonP5SZZznYJMa3Vp8ks5vLHq_gaJpZM4ZMLKj
.
--
William J. Schroeder, PhD
Kitware, Inc. - Building the World's Technical Computing Software
28 Corporate Drive
Clifton Park, NY 12065
will.[email protected]
http://www.kitware.com
(518) 881-4902
@wschroed good point. We can take an incremental approach. First to PolyData so we can just visualize them. Then to VTK Implicit Functions. We likely find that we want / need the implicit functions for cropping, cutting, etc., but individual conversions will take more time. And, vtk.js Implicit Functions support can also mature in the process.
Most helpful comment
Yes! :space_invader: :sparkler: :sparkling_heart:
Starting on this.
Inserted 4.b) - ITK SpatialObject to VTK PolyData :-D