Operating system: Windows 10
Slicer version: 4.11
Overall Goal: Visualizing the brain in Real-time to design and follow a trajectory using a stylus tracked with optical tracker.
Problem: Present a real-time cross section of the brain with respect to Stylus. Please check attached images for illustration.
Currently, i am in a position where the stylus is calibrated, registration took place between real and 3D model of a skull phantom and showing the stylus on a fused MRI/CT scan image using Volume Reslice Driver.
My next step is to do the shown above as an attempt to design a safe trajectory.
Preserving the segmented tumor and cross-section the surrounding.
How doable is that? Or is it something we can create a module for?
Thank you in advance.
Everything that is shown in the images above is easily doable (you just need to enable the feature that you need).
What exactly do you miss?
3D display of the tumor? You can enable that by clicking “Show 3D” button in Segment Editor module.
Thank you for your reply Andras,
What i am seeking is to provide an active cross-section of the brain relative to stylus motion. That is the deeper the stylus goes inside the phantom the deeper the cross section is shown in 3D view. From the image i attached previously you can see how when the stylus was far from the skull the cross section was shallow, the closer it goes the deeper the cross section without affecting the segmented tumor.
Please see the Youtube video between seconds 1:20 to 1:30 the 3D overview section.
Thank you so much
What happens in the 3D view in the video can be achieved by enabling “Crop” in the Volume Rendering module, and apply a transform node on the ROI used for cropping the volume in the 3D view. If that transform node is transformed by the StylusTipTo… transform, then the volume will be cropped relative to the StylusTip position. The tumor contour is a different node, a yellow surface model not cropped by the ROI, so that is always visible.
I will test it right the way!,
Thank you all so much for your support.
We have a problem similar to yours. What type of navigation device are you using here? Can I contact you if possible?