I am using the hallow module to create a hallow model, with the desired width. However, when I check the model’s thickness in meshmixer it seems like the thickness is roughly half of the desired width. Would you please suggest a way to measure the thickness of the generated hallow model in the Slicer and also compare the results in any other 3D software to make sure that the generated model has the same thickness?
Thank you for your help.
Thanks for reporting this. This was an issue in Slicer-4.10 and it was fixed in some time ago in Slicer-4.11.
Thank you for your reply. I imported my segmentation in Slicer 4.11, however when I try to grow the margin of the segmentation with the desired thickness, it has almost the same thickness as previous(almost half of the desire value). Is the problem fixed both for hallow and the the margin modules?
Margin size in “Margin” effect still refers to overall margin (the structure will be wider by the margin size in total, so width is increased by half the margin size on all sides). I agree that it is confusion and it should work the same way as hollow effect.
We have a pending pull request by @sunderlandkyl that hugely improves speed of these effects for large values - we’ll change interpretation of the margin size when that gets integrated.
Fast margin computation will be available in Slicer Preview Release from tomorrow (rev28764 or later).
Thank you so much for this improvement to @Sunderlandkyl and Prof @lassoan.
It works perfectly !!!
Just for the information,
What was actually changed ?
What is the algorithm/science behind this ? If you have a publication please link it.
I read somewhere along the way that something was changing from marching cubes to flying edge algorithm ? was this something like that ?
Margin computation was previously computed using kernel based erosion and dilation (vtkImageDilateErode3D).
We updated the margin and hollow effects to calculate and threshold a distance map using ITK (itk::SignedMaurerDistanceMapImageFilter, Insight Journal paper).