Open reneeotten opened 1 year ago
I've locally updated the API usage and tested up to 1.9 which works, but seems like as soon as I use vtk-m 2.0.0, isosurface generation is incorrect. I'll look into it further this week, but may have to wait if this is an issue with vtk-m.
can support be added for latest
VTK-m
release (currently v2.0.0)?