Difference between revisions of "Documentation/4.3/Extensions/CleaverExtension"
Line 97: | Line 97: | ||
|}<br> | |}<br> | ||
− | Sample data: | + | Sample data: [[Media:CleaverSampleData.zip]] |
− | * Option 1 - Use MRHead-label.nrrd + MRHeader-label-inverse.nrrd. | + | * Option 1 - Use Cleaver-MRHead-label.nrrd + Cleaver-MRHeader-label-inverse.nrrd. |
− | * Option 2a - Use MRHead-label-shifted.nrrd and let Cleaver infer the inverse. | + | * Option 2a - Use Cleaver-MRHead-label-shifted.nrrd and let Cleaver infer the inverse. |
− | * Option 2b - Use | + | * Option 2b - Use Cleaver-MRHead-label-shifted-Gaussian.nrrd and let Cleaver infer the inverse. This is a Gaussian smoothed version of option 2a to show how a smooth function can prevent stair-stepping artefacts. |
<!-- ---------------------------- --> | <!-- ---------------------------- --> |
Latest revision as of 02:20, 4 November 2014
Home < Documentation < 4.3 < Extensions < CleaverExtension
For the latest Slicer documentation, visit the read-the-docs. |
Introduction and Acknowledgements
Developed at the SCI Institute, University of Utah. Author: Jonathan Bronson Module DescriptionCleaverExtension is a Slicer CLI Module that takes a set of NRRD Volumes and creates a set of tetrahedral meshes
to import into the Slicer MRML. Based on the "Lattice Cleaving" algorithm (see References), this method is theoretically guaranteed to produce valid meshes with bounded dihedral angles, while still conforming to multimaterial material surfaces. Empirically these bounds have been shown to be significant. Use CasesPanels and their use
Cleaver operates on indicator functions (each defined by an input volume), and requires at least two. If you provide only a single function, Cleaver attempts to make an 'inverse' material for you automatically, by multiplying the field by -1 (therefore one material should have voxel value of X and the other material should have voxel value of -X). One other thing you might want to watch out for is you're using a very discontinuous input field. This is going to lead to stair-stepping artifacts on your output mesh. Providing smooth input functions will eliminate this problem. Tutorials
Sample data: Media:CleaverSampleData.zip
References
Information for DevelopersFor technical questions or problems, please use contacts in the introduction. |