# Viskores to replace VTK-m

**URL:** <https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579>\
**Category:** Development\
**Created:** [May 7, 2025, 5:04pm UTC](https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579 "2025-05-07T17:04:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave-Allured](https://discourse.vtk.org/user_avatar/discourse.vtk.org/dave-allured/32/7698_2.png) [@Dave-Allured](https://discourse.vtk.org/u/Dave-Allured)\
**Post date:** [May 7, 2025, 5:04pm UTC](https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579/1 "2025-05-07T17:04:31Z")

</div>

Viskores is the open source successor for VTK-m, which is being discontinued. What is the VTK support plan for the Viskores transition?

[https://gitlab.kitware.com/vtk/vtk-m/-/blob/master/README.md](https://gitlab.kitware.com/vtk/vtk-m/-/blob/master/README.md)

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)\
**Post date:** [May 7, 2025, 6:56pm UTC](https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579/2 "2025-05-07T18:56:04Z")

</div>

There’s [an MR](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/12079) to import viskores into VTK. Note that this is still disabled; once it is in, we’ll work on integrating it and replacing VTK-m.

Cc: @vbolea

---

<div class="post-metadata">

**Author:** ![Dave-Allured](https://discourse.vtk.org/user_avatar/discourse.vtk.org/dave-allured/32/7698_2.png) [@Dave-Allured](https://discourse.vtk.org/u/Dave-Allured)\
**Post date:** [May 7, 2025, 7:27pm UTC](https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579/3 "2025-05-07T19:27:22Z")

</div>

Very good. Since Visktores is a large complicated package, I recommend supporting it as external only, rather than bundling.

---

<div class="post-metadata">

**Author:** ![vbolea](https://discourse.vtk.org/user_avatar/discourse.vtk.org/vbolea/32/4060_2.png) [@vbolea](https://discourse.vtk.org/u/vbolea)\
**Post date:** [May 7, 2025, 7:35pm UTC](https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579/4 "2025-05-07T19:35:32Z")

</div>

We are working in keeping it still as an internal (Snapshot) package while also allowing users to use an external Viskores (such as in spack). We want to keep it bundled since Viskores is an important dependency of VTK that adds parallel VTK algorithms which allows VTK to leverage device adaptors such as GPUs. Having it bundled eases CI, one-time deployments, and package managers that does not have Viskores packaged.

---

<div class="post-metadata">

**Author:** ![seanm](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/s/a88e4f/32.png) [@seanm](https://discourse.vtk.org/u/seanm)\
**Post date:** [June 17, 2025, 7:47pm UTC](https://discourse.vtk.org/t/viskores-to-replace-vtk-m/15579/5 "2025-06-17T19:47:33Z")

</div>

You might want to update the list of “Popular Projects” on the gitlab main page (log out, or use private tab):

[https://gitlab.kitware.com/users/sign\_in](https://gitlab.kitware.com/users/sign_in)

it still lists vtk-m.