New feature: Thick slab reconstruction from slice controllers and views

Support
1

Thick slab reconstruction (TSR) can now be enabled and modified from the slice controllers and slice views!

Enabling thick slab reconstruction as well as selection of the composite method (min, max, mean or sum) has been available through the python console.

Now these options are available through both the slice controller and the right-click context menu on the slice views. If the interactive option is selected, the thickness, angle and position of the TSR can be adjusted by moving the slice intersections in the slice views.

Slice Controller (Default) Slice Controller (Slab Enabled) Slice Controller (Slab Enabled + Interactive)
image image image
Slice Viewer (Handle Interaction ) Slice Viewer (Right-click context menu) Slice Viewer (slice intersection & Slab & Interactive) Slice Viewer (Red & Yellow Slab enabled then Linked)
image image image image

These features are currently available in the preview version of 3D Slicer.

Issue 1, PR 1 (slice controller implementation)
Issue 2, PR 2 (slice views implementation)

5 Likes
2

This slice controller is a very good news!
How can I use it?

3

After installing Slicer, are you able to enable “Thick Slab Reconstruction” from the Slicer controller ?

4

Hello, this is a great feature. Is there a way to remove slabs before exporting a snapshot ? It would be really great, since some details can be hided from the slabs

6

can i create a lateral cephalometry from skull ct with thick slab ?

7

Hi, very useful tool! Thanks.
However, the slab thickness seems to not work correctly on my data. As you can see in the capture below, the two red lines already cover the whole volume, but the MIP image in the Red view does not really show all vessels. If I increase the interval between the two red lines, more vessels will appear on the MIP image. Do you know why? And how to fix it?

ThickSlabRecon-Thickness
ThickSlabRecon-Thickness1792Ă—1317 122 KB

8

@ZhsChen can you share the data or reproduce on public data?

9

Hi Pieper, I just tried on the DZ-MR_1 data in the sample dataset CBCT-MR Head, same problem occurred. In the two captures below, the projection slabes both cover the whole head, but the MIP images are different.

thickness1
thickness11504Ă—921 146 KB

thickness2
thickness21505Ă—922 144 KB

10

Can you explain why you think the MIP is incorrect?

11

In the two captures above, I expect the two MIPs (in the Red view) to be exactly the same, since in both images the projection slab covers the whole head (the region outside the head has zero or very low value, and will not be projected to the MIPs).

12

But they are different. This suggests that the real slab used for projection is smaller than the slab between the two red lines.

13

This is the code that sets up thick slab reslicing parameters:

Most likely the slabNumberOfSlices and slabSliceSpacingFraction computation has to be fixed.