Open luciemac opened 5 years ago
This is an issue with multiple volume rendering in vtk.js. (Reference issue: https://github.com/Kitware/vtk-js/issues/473)
It would be nice to generate a surface of the labelmap, but that's more costly. I will explore that option however.
Let's talk, I have an algo for it in JS that will need some cleanup. That way you can take over.
In addition to #473, and surface generation, both of which would be good to address, #936 is of interest here. The label map and the image are sampled on the same grid.
Hey, I just wanted to point out that unfortunately vtkjs #936 (i.e. multiple components) is probably not a good solution to the labelmap problem, as its very common to have to switch out different labelmaps on the fly, and it'd be really inefficient to have to copy this labelmap into the component of the volume. Also the same labelmap might be overlayed onto different source data, again making this an unfeasible solution.
So I think multiple volume rendering would be the way to go for this use case.
I understand I'm slightly necroposting, apologies if there is a more recent status update on this, is there any update on this issue?
Thanks.
In 3D view, once a labeled area is defined, it seems to be rendered in front of the tooth.