home.social

#vtk — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vtk, aggregated by home.social.

  1. I'm currently looking for a way to bring together my experience with #SmoothedParticleHydroynamics and #remoteSensing, and as part of this process I also wrote a converter (in #Julia, because this has to fit within some existing code which I wrote in that language) that allows me to export satellite imagery as #VTK unstructured grids, so that I can visualize them in #ParaView

    It feels weird because ParaView *really* isn't suited for #GIS work, but in this case it turns out to be The Right Tool For The Job™.

    #SPH

  2. I'm currently looking for a way to bring together my experience with #SmoothedParticleHydroynamics and #remoteSensing, and as part of this process I also wrote a converter (in #Julia, because this has to fit within some existing code which I wrote in that language) that allows me to export satellite imagery as #VTK unstructured grids, so that I can visualize them in #ParaView

    It feels weird because ParaView *really* isn't suited for #GIS work, but in this case it turns out to be The Right Tool For The Job™.

    #SPH

  3. I'm currently looking for a way to bring together my experience with #SmoothedParticleHydroynamics and #remoteSensing, and as part of this process I also wrote a converter (in #Julia, because this has to fit within some existing code which I wrote in that language) that allows me to export satellite imagery as #VTK unstructured grids, so that I can visualize them in #ParaView

    It feels weird because ParaView *really* isn't suited for #GIS work, but in this case it turns out to be The Right Tool For The Job™.

    #SPH

  4. I'm currently looking for a way to bring together my experience with #SmoothedParticleHydroynamics and #remoteSensing, and as part of this process I also wrote a converter (in #Julia, because this has to fit within some existing code which I wrote in that language) that allows me to export satellite imagery as #VTK unstructured grids, so that I can visualize them in #ParaView

    It feels weird because ParaView *really* isn't suited for #GIS work, but in this case it turns out to be The Right Tool For The Job™.

    #SPH

  5. I'm currently looking for a way to bring together my experience with #SmoothedParticleHydroynamics and #remoteSensing, and as part of this process I also wrote a converter (in #Julia, because this has to fit within some existing code which I wrote in that language) that allows me to export satellite imagery as #VTK unstructured grids, so that I can visualize them in #ParaView

    It feels weird because ParaView *really* isn't suited for #GIS work, but in this case it turns out to be The Right Tool For The Job™.

    #SPH

  6. I was making great progress on a probably-useless #python #vtk #dataviz and had gotten to the critical step: compute the intersections of these #3d polymeshes to show the interesting part.....

    ...and it keeps segfaulting.

    Internet suggests the polymeshes may be imperfect but cleaning them doesn't help. I'm dejected. I wanna work on it but I don't want to spend most of a weekend debugging a single problem

  7. I was making great progress on a probably-useless #python #vtk #dataviz and had gotten to the critical step: compute the intersections of these #3d polymeshes to show the interesting part.....

    ...and it keeps segfaulting.

    Internet suggests the polymeshes may be imperfect but cleaning them doesn't help. I'm dejected. I wanna work on it but I don't want to spend most of a weekend debugging a single problem

  8. I was making great progress on a probably-useless and had gotten to the critical step: compute the intersections of these polymeshes to show the interesting part.....

    ...and it keeps segfaulting.

    Internet suggests the polymeshes may be imperfect but cleaning them doesn't help. I'm dejected. I wanna work on it but I don't want to spend most of a weekend debugging a single problem

  9. I was making great progress on a probably-useless #python #vtk #dataviz and had gotten to the critical step: compute the intersections of these #3d polymeshes to show the interesting part.....

    ...and it keeps segfaulting.

    Internet suggests the polymeshes may be imperfect but cleaning them doesn't help. I'm dejected. I wanna work on it but I don't want to spend most of a weekend debugging a single problem

  10. I was making great progress on a probably-useless #python #vtk #dataviz and had gotten to the critical step: compute the intersections of these #3d polymeshes to show the interesting part.....

    ...and it keeps segfaulting.

    Internet suggests the polymeshes may be imperfect but cleaning them doesn't help. I'm dejected. I wanna work on it but I don't want to spend most of a weekend debugging a single problem

  11. I love #pyqtgraph for 2D scientific and #dataviz #graphs in #python. And now I'm starting to really love #vtk for 3D.

    vtk.org/

    It has a lot of the same #science adjacent type plotting. It works well with python. (And there's a #javascript #api but I haven't used it...yet). And it is *extremely fast*.

    The only problem is that there's a lot to it and I don't really understand the workflow. (I feel like there's an extra layer. There's a "source", a "mapper", an "actor" and a "renderer". One of those seems superfluous.)

    There are a lot of examples on their site and elsewhere. And there's a lot of documentation. But I haven't yet found a good combination tutorial that has worked examples that are also explained.

    I really just have to use it more and get it into my head.

    Fortunately, I have a weird #math/#geometry/#orbitalmechanics thing I want to try to solve (or at least visualize). Intersections of multiple ellipsoids and cones....

  12. I love #pyqtgraph for 2D scientific and #dataviz #graphs in #python. And now I'm starting to really love #vtk for 3D.

    vtk.org/

    It has a lot of the same #science adjacent type plotting. It works well with python. (And there's a #javascript #api but I haven't used it...yet). And it is *extremely fast*.

    The only problem is that there's a lot to it and I don't really understand the workflow. (I feel like there's an extra layer. There's a "source", a "mapper", an "actor" and a "renderer". One of those seems superfluous.)

    There are a lot of examples on their site and elsewhere. And there's a lot of documentation. But I haven't yet found a good combination tutorial that has worked examples that are also explained.

    I really just have to use it more and get it into my head.

    Fortunately, I have a weird #math/#geometry/#orbitalmechanics thing I want to try to solve (or at least visualize). Intersections of multiple ellipsoids and cones....

  13. I love for 2D scientific and in . And now I'm starting to really love for 3D.

    vtk.org/

    It has a lot of the same adjacent type plotting. It works well with python. (And there's a but I haven't used it...yet). And it is *extremely fast*.

    The only problem is that there's a lot to it and I don't really understand the workflow. (I feel like there's an extra layer. There's a "source", a "mapper", an "actor" and a "renderer". One of those seems superfluous.)

    There are a lot of examples on their site and elsewhere. And there's a lot of documentation. But I haven't yet found a good combination tutorial that has worked examples that are also explained.

    I really just have to use it more and get it into my head.

    Fortunately, I have a weird /#geometry/#orbitalmechanics thing I want to try to solve (or at least visualize). Intersections of multiple ellipsoids and cones....

  14. I love #pyqtgraph for 2D scientific and #dataviz #graphs in #python. And now I'm starting to really love #vtk for 3D.

    vtk.org/

    It has a lot of the same #science adjacent type plotting. It works well with python. (And there's a #javascript #api but I haven't used it...yet). And it is *extremely fast*.

    The only problem is that there's a lot to it and I don't really understand the workflow. (I feel like there's an extra layer. There's a "source", a "mapper", an "actor" and a "renderer". One of those seems superfluous.)

    There are a lot of examples on their site and elsewhere. And there's a lot of documentation. But I haven't yet found a good combination tutorial that has worked examples that are also explained.

    I really just have to use it more and get it into my head.

    Fortunately, I have a weird #math/#geometry/#orbitalmechanics thing I want to try to solve (or at least visualize). Intersections of multiple ellipsoids and cones....

  15. I love #pyqtgraph for 2D scientific and #dataviz #graphs in #python. And now I'm starting to really love #vtk for 3D.

    vtk.org/

    It has a lot of the same #science adjacent type plotting. It works well with python. (And there's a #javascript #api but I haven't used it...yet). And it is *extremely fast*.

    The only problem is that there's a lot to it and I don't really understand the workflow. (I feel like there's an extra layer. There's a "source", a "mapper", an "actor" and a "renderer". One of those seems superfluous.)

    There are a lot of examples on their site and elsewhere. And there's a lot of documentation. But I haven't yet found a good combination tutorial that has worked examples that are also explained.

    I really just have to use it more and get it into my head.

    Fortunately, I have a weird #math/#geometry/#orbitalmechanics thing I want to try to solve (or at least visualize). Intersections of multiple ellipsoids and cones....

  16. 🛡️ CRITICAL heap use-after-free in Kitware VTK ≤9.5.0 (CVE-2025-57108) — malicious GLTF files can trigger code execution or crashes via vtkGLTFDocumentLoader. No patch yet: restrict GLTF input, monitor for updates, and use memory safety tools. radar.offseq.com/threat/cve-20 #OffSeq #VTK #CVE202557108

  17. 🛡️ CRITICAL heap use-after-free in Kitware VTK ≤9.5.0 (CVE-2025-57108) — malicious GLTF files can trigger code execution or crashes via vtkGLTFDocumentLoader. No patch yet: restrict GLTF input, monitor for updates, and use memory safety tools. radar.offseq.com/threat/cve-20 #OffSeq #VTK #CVE202557108

  18. 🛡️ CRITICAL heap use-after-free in Kitware VTK ≤9.5.0 (CVE-2025-57108) — malicious GLTF files can trigger code execution or crashes via vtkGLTFDocumentLoader. No patch yet: restrict GLTF input, monitor for updates, and use memory safety tools. radar.offseq.com/threat/cve-20 #OffSeq #VTK #CVE202557108

  19. VTK - công ty con của Viettel đang mở rộng từ xây dựng hạ tầng viễn thông (2G-5G) sang lĩnh vực thiết kế dân dụng, công nghiệp và nội thất công trình. Bước tiến chiến lược "lấn sân" thể hiện năng lực đa dạng hóa của tập đoàn quốc phòng - viễn thông lớn nhất Việt Nam.

    #Viettel #VTK #thietkenoithat #haotang #dando #mobile #5G #infrastructure #design #Vietnam

    vietnamnet.vn/cong-ty-con-cua-

  20. #dataviz is critical, but I don't think in pictures, I think in spatial relations and movement (is this an #adhd thing?)

    Movement happens in time and you usually want to viz the time axis all at once, so I've trained myself to turn "$variable vs t" into mental motion

    Other times you need an interactive #ux and that usually means 3D

    I love love love #pyqtgraph for #python plotting but they will be the first to tell you the 3D needs some love

    My punfully-named work project has proved to be a hit[1] and I managed to get an 30y-experienced #software #developer *with an #astronomy degree* assigned to it. (This is a #space application)

    She agreed that the 3D portion was neat but hard to use. She found #vtk, which seems to be the perfect partner because it does 3D really well, stays out of 2D and has a #pyqt connector.

    I just worked through a tutorial and, yeah, this could be a huge breakthrough in my viz apps.

    [1]They think they want to change the pun name but they are wrong. An unforgettable name is money in the bank.

  21. #dataviz is critical, but I don't think in pictures, I think in spatial relations and movement (is this an #adhd thing?)

    Movement happens in time and you usually want to viz the time axis all at once, so I've trained myself to turn "$variable vs t" into mental motion

    Other times you need an interactive #ux and that usually means 3D

    I love love love #pyqtgraph for #python plotting but they will be the first to tell you the 3D needs some love

    My punfully-named work project has proved to be a hit[1] and I managed to get an 30y-experienced #software #developer *with an #astronomy degree* assigned to it. (This is a #space application)

    She agreed that the 3D portion was neat but hard to use. She found #vtk, which seems to be the perfect partner because it does 3D really well, stays out of 2D and has a #pyqt connector.

    I just worked through a tutorial and, yeah, this could be a huge breakthrough in my viz apps.

    [1]They think they want to change the pun name but they are wrong. An unforgettable name is money in the bank.

  22. is critical, but I don't think in pictures, I think in spatial relations and movement (is this an thing?)

    Movement happens in time and you usually want to viz the time axis all at once, so I've trained myself to turn "$variable vs t" into mental motion

    Other times you need an interactive and that usually means 3D

    I love love love for plotting but they will be the first to tell you the 3D needs some love

    My punfully-named work project has proved to be a hit[1] and I managed to get an 30y-experienced *with an degree* assigned to it. (This is a application)

    She agreed that the 3D portion was neat but hard to use. She found , which seems to be the perfect partner because it does 3D really well, stays out of 2D and has a connector.

    I just worked through a tutorial and, yeah, this could be a huge breakthrough in my viz apps.

    [1]They think they want to change the pun name but they are wrong. An unforgettable name is money in the bank.

  23. #dataviz is critical, but I don't think in pictures, I think in spatial relations and movement (is this an #adhd thing?)

    Movement happens in time and you usually want to viz the time axis all at once, so I've trained myself to turn "$variable vs t" into mental motion

    Other times you need an interactive #ux and that usually means 3D

    I love love love #pyqtgraph for #python plotting but they will be the first to tell you the 3D needs some love

    My punfully-named work project has proved to be a hit[1] and I managed to get an 30y-experienced #software #developer *with an #astronomy degree* assigned to it. (This is a #space application)

    She agreed that the 3D portion was neat but hard to use. She found #vtk, which seems to be the perfect partner because it does 3D really well, stays out of 2D and has a #pyqt connector.

    I just worked through a tutorial and, yeah, this could be a huge breakthrough in my viz apps.

    [1]They think they want to change the pun name but they are wrong. An unforgettable name is money in the bank.

  24. #dataviz is critical, but I don't think in pictures, I think in spatial relations and movement (is this an #adhd thing?)

    Movement happens in time and you usually want to viz the time axis all at once, so I've trained myself to turn "$variable vs t" into mental motion

    Other times you need an interactive #ux and that usually means 3D

    I love love love #pyqtgraph for #python plotting but they will be the first to tell you the 3D needs some love

    My punfully-named work project has proved to be a hit[1] and I managed to get an 30y-experienced #software #developer *with an #astronomy degree* assigned to it. (This is a #space application)

    She agreed that the 3D portion was neat but hard to use. She found #vtk, which seems to be the perfect partner because it does 3D really well, stays out of 2D and has a #pyqt connector.

    I just worked through a tutorial and, yeah, this could be a huge breakthrough in my viz apps.

    [1]They think they want to change the pun name but they are wrong. An unforgettable name is money in the bank.

  25. This is an attempt to create a metal/steel-like material... and in order to add a bit more appeal on top, I also tried to mimic a not yet fully polished 'function surface/coating'. The model is a low-poly mesh from Sketchfab lnkd.in/e2xCdwJh Yes, the mesh is a bit odd... the wall-thickness between the cylinders is too thin to make sense in the real world... and it is missing coolant passages. #vtk #shader #pbr #rendering

  26. This is an attempt to create a metal/steel-like material... and in order to add a bit more appeal on top, I also tried to mimic a not yet fully polished 'function surface/coating'. The model is a low-poly mesh from Sketchfab lnkd.in/e2xCdwJh Yes, the mesh is a bit odd... the wall-thickness between the cylinders is too thin to make sense in the real world... and it is missing coolant passages. #vtk #shader #pbr #rendering

  27. More messing around with vtk 9.4.0... this time order-independent transparency and iso-surface extraction... #OpenGL #vtk #dataViz

  28. More messing around with vtk 9.4.0... this time order-independent transparency and iso-surface extraction... #OpenGL #vtk #dataViz

  29. Cutting/clipping with vtk 9.4.0 *sigh* sure it's only a low-resolution data-set, but it looks horrible with this vertex-based coloring... it's going to be some work to patch this to make it use proper interpolation using a fragment-shader based approach #OpenGL #vtk #dataViz #computerGraphics

  30. Cutting/clipping with vtk 9.4.0 *sigh* sure it's only a low-resolution data-set, but it looks horrible with this vertex-based coloring... it's going to be some work to patch this to make it use proper interpolation using a fragment-shader based approach #OpenGL #vtk #dataViz #computerGraphics

  31. After more than 15 years i am stepping into the world of vtk again... 9.4.0 to be precise, which was just released about two weeks ago. Let's see what changed, what remained the same and what was added. #computerGraphics #vtk #OpenGL

  32. After more than 15 years i am stepping into the world of vtk again... 9.4.0 to be precise, which was just released about two weeks ago. Let's see what changed, what remained the same and what was added. #computerGraphics #vtk #OpenGL

  33. ~fluencyCAD~

    Progressed into sketch projection from and to 2D. I think this is a cleaner approach for drawing.

    Next stage will be additional operations like cutting holes and timeline logic.

    Intention is to have CAD geared towards maker with a focused UI with static layout so you can develp "muscle memory".
    I´m pretty happy already as I completely ruled out writing a CAD software at all.

    Project can be assisted by donating for tea here:
    https://ko-fi.com/raise_project

    #sdfcad #solvespace #fluencycad #mechanicaldesign #vtk #python

  34. ~fluencyCAD~

    Progressed into sketch projection from and to 2D. I think this is a cleaner approach for drawing.

    Next stage will be additional operations like cutting holes and timeline logic.

    Intention is to have CAD geared towards maker with a focused UI with static layout so you can develp "muscle memory".
    I´m pretty happy already as I completely ruled out writing a CAD software at all.

    Project can be assisted by donating for tea here:
    https://ko-fi.com/raise_project

    #sdfcad #solvespace #fluencycad #mechanicaldesign #vtk #python

  35. ~fluencyCAD~

    Progressed into sketch projection from and to 2D. I think this is a cleaner approach for drawing.

    Next stage will be additional operations like cutting holes and timeline logic.

    Intention is to have CAD geared towards maker with a focused UI with static layout so you can develp "muscle memory".
    I´m pretty happy already as I completely ruled out writing a CAD software at all.

    Project can be assisted by donating for tea here:
    https://ko-fi.com/raise_project

    #sdfcad #solvespace #fluencycad #mechanicaldesign #vtk #python

  36. ~fluencyCAD~

    Progressed into sketch projection from and to 2D. I think this is a cleaner approach for drawing.

    Next stage will be additional operations like cutting holes and timeline logic.

    Intention is to have CAD geared towards maker with a focused UI with static layout so you can develp "muscle memory".
    I´m pretty happy already as I completely ruled out writing a CAD software at all.

    Project can be assisted by donating for tea here:
    https://ko-fi.com/raise_project

    #sdfcad #solvespace #fluencycad #mechanicaldesign #vtk #python

  37. #FluidX3D v2.13 is out, providing faster #VTK export with automatic SI unit conversion and a variety of bug fixes!
    Full release notes: github.com/ProjectPhysX/FluidX
    #GPU #CFD #OpenCL #GPGPU #HPC #GitHub

  38. #FluidX3D v2.13 is out, providing faster #VTK export with automatic SI unit conversion and a variety of bug fixes!
    Full release notes: github.com/ProjectPhysX/FluidX
    #GPU #CFD #OpenCL #GPGPU #HPC #GitHub

  39. #FluidX3D v2.13 is out, providing faster #VTK export with automatic SI unit conversion and a variety of bug fixes!
    Full release notes: github.com/ProjectPhysX/FluidX
    #GPU #CFD #OpenCL #GPGPU #HPC #GitHub

  40. #FluidX3D v2.13 is out, providing faster #VTK export with automatic SI unit conversion and a variety of bug fixes!
    Full release notes: github.com/ProjectPhysX/FluidX
    #GPU #CFD #OpenCL #GPGPU #HPC #GitHub

  41. #FluidX3D v2.13 is out, providing faster #VTK export with automatic SI unit conversion and a variety of bug fixes!
    Full release notes: github.com/ProjectPhysX/FluidX
    #GPU #CFD #OpenCL #GPGPU #HPC #GitHub

  42. @cosmoscalibur Hmmmm....I've rejected #vtk more than once over the years as being overkill. But the amount of kill I need has grown, so maybe it's time to make the jump. #matplotlib is definitely not cutting it anymore.

  43. @cosmoscalibur Hmmmm....I've rejected #vtk more than once over the years as being overkill. But the amount of kill I need has grown, so maybe it's time to make the jump. #matplotlib is definitely not cutting it anymore.

  44. @cosmoscalibur Hmmmm....I've rejected more than once over the years as being overkill. But the amount of kill I need has grown, so maybe it's time to make the jump. is definitely not cutting it anymore.

  45. @cosmoscalibur Hmmmm....I've rejected #vtk more than once over the years as being overkill. But the amount of kill I need has grown, so maybe it's time to make the jump. #matplotlib is definitely not cutting it anymore.

  46. @cosmoscalibur Hmmmm....I've rejected #vtk more than once over the years as being overkill. But the amount of kill I need has grown, so maybe it's time to make the jump. #matplotlib is definitely not cutting it anymore.

  47. CW: From birdsite

    Who wrote dialogues for #VTK 😂

  48. CW: From birdsite

    Who wrote dialogues for 😂