Difference between revisions of "Documentation/4.2/Modules/ModelMaker"
(Nightly -> 4.2)
(Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887)
|Line 1:||Line 1:|
<!-- ---------------------------- -->
<!-- ---------------------------- -->
Latest revision as of 07:44, 14 June 2013Home < Documentation < 4.2 < Modules < ModelMaker
For the latest Slicer documentation, visit the 4.10 page.
Introduction and Acknowledgements
The Modelmaker is used to create 3D surface models from segmented image data, called label maps. Label maps can be the result of automated segmentation or interactive editing. References give more details on the algorithm.
Create 3D surface models from segmented data.
Models are imported into Slicer under a model hierarchy node in a MRML scene. The model colors are set by the color table associated with the input volume (these colours will only be visible if you load the model scene file).
If you specify a list of Labels, it will over ride any start/end label settings.
If you clickGenerate Allit will over ride the list of lables and any start/end label settings.
Model Maker Settings:
You can set the number of smoothing iterations, target reduction in number of polygons (decimal percentage). Use 0 and 1 if you wish no smoothing nor decimation.
You can set the flags to split normals or generate point normals in this pane as well.
You can save a copy of the models after intermediate steps (marching cubes, smoothing, and decimation if not joint smoothing, otherwise just after decimation); these models are not saved in the mrml file, turn off deleting temporary files first in the python window:
Most frequently used for these scenarios:
- Input Volume: Input label map. The Input Volume drop down menu is populated with the label map volumes that are present in the scene, select one from which to generate models.
- Models: Generated models, under a model hierarchy node. Models are imported into Slicer under a model hierarchy node, and their colors are set by the color table associated with the input label map volume. The model hierarchy node must be created before running the model maker, by selecting Create New ModelHierarchy from the Models drop down menu. If you're running from the command line, a model hierarchy node in a new mrml scene will be created for you.
- Create Multiple
- Model Name: Name to use for this model. Any text entered in the entry box will be the starting string for the created model file names. The label number and the color name will also be part of the file name. If making multiple models, use this as a prefix to the label and color name.
- Generate All Models: Generate models for all labels in the input volume. select this option if you want to create all models that correspond to all values in a labelmap volume (using the Joint Smoothing option below is useful with this option). Ignores Labels, Start Label, End Label settings. Skips label 0.
- Model Maker Parameters
- Labels: A comma separated list of label values from which to make models. f you specify a list of Labels, it will override any start/end label settings. If you click Generate All Models it will override the list of labels and any start/end label settings.
- Start Label: If you want to specify a continuous range of labels from which to generate models, enter the lower label here. Voxel value from which to start making models. Used instead of the label list to specify a range (make sure the label list is empty or it will over ride this).
- End Label: If you want to specify a continuous range of labels from which to generate models, enter the higher label here. Voxel value up to which to continue making models. Skip any values with zero voxels.
- Skip Un-Named Labels: Select this to not generate models from labels that do not have names defined in the color look up table associated with the input label map. If true, only models which have an entry in the color table will be generated. If false, generate all models that exist within the label range.
- Joint Smoothing: This will ensure that all resulting models fit together smoothly, like jigsaw puzzle pieces. Otherwise the models will be smoothed independently and may overlap.
- Smooth: Here you can set the number of smoothing iterations. Use 0 if you wish no smoothing.
- Filter Type: You can control the type of smoothing done on the models by selecting a filter type of either Sinc or Laplacian.
- Decimate: Chose the target reduction in number of polygons as a decimal percentage (between 0 and 1) of the number of polygons. Use 1 if you wish no decimation.
- Split Normals: Splitting normals is useful for visualizing sharp features. However it creates holes in surfaces which affects measurements.
- Point Normals: Turn this flag on if you wish to calculate the normal vectors for the points.
- Pad: Pad the input volume with zero value voxels on all 6 faces in order to ensure the production of closed surfaces. Sets the origin translation and extent translation so that the models still line up with the unpadded input volume.
- Save Intermediate Models: You can save a copy of the models after each of the intermediate steps (marching cubes, smoothing, and decimation if not joint smoothing, otherwise just after decimation). These intermediate models are not saved in the mrml file, you have to load them manually after turning off deleting temporary files in they python console (View ->Python Interactor) using the following command slicer.modules.modelmaker.cliModuleLogic().DeleteTemporaryFilesOff().
- Debug: turn this flag on in order to see debugging output (look in the Error Log window that is accessed via the View menu)
- Grey Scale Model Maker generates models from grey scale images.
- The Volumes and Models modules are required
Information for Developers
|Section under construction.|