Best Practices for Segment Mesher, Cleaver

Support
, ,
1

Hello,

Our team is trying to use the segment mesher extension on a multi-material model of breast tissue, segmented from an MRI dataset. We are having great success, but still have some questions related to best practices for implementing this plug-in.

Our process/pipeline:

  1. In general, we segment three (3) materials: skin, breast tissue (adipose + glandular), and tumor/mass
  2. We use segment mesher to create a tetrahedral mesh
  3. We perform mechanical simulation on the mesh using FEBio

Our issue:

  1. We currently get a very fine mesh on the outside surface of our model (Figure 1, below). The screenshot is from FEBio. This mesh follows the “stepping” of the model due to the scan. We have tried median and Gaussian filters on the segmentation and the result above is one of the best results we have achieved. I have played with the cleaver parameters, but varying these ends-up affecting the mesh internal features.

Does anyone have any advice on how to segment and smooth data prior to meshing?

Figure 1: Fine Mesh

Also, separate issue I have found with the segment mesher plug-in:

  1. The .VTK file in the temp folder that results from cleaver’s meshing is ASCII while the file saved from the Slicer interface is Binary. Is there a way for the plug-in to use/save the ASCII file? Programs like FEBioStudio do not have .VTK Binary readers
2

To fix this, resample the input volume to have isotropic spacing (cube shaped voxels) before you start segmentation, using Crop volume module.

Other than that, I would recommend to experiment with meshing parameters described here on a small volume.

When you save the mesh in Slicer, uncheck “Compress” option in Save data window to save as ASCII.

3

Can You please help me find the “Compress” option in save data window. I need to save volumetric mesh as ascii.

save data