Bender/Documentation/1.1/Modules/VolumeSkinning: Difference between revisions
No edit summary |
|||
| Line 28: | Line 28: | ||
| align="right" | [[Image:VolumeSkinningPanel-1.0.png|thumb|550px|Volume Skinning panel]] | | align="right" | [[Image:VolumeSkinningPanel-1.0.png|thumb|550px|Volume Skinning panel]] | ||
|} | |} | ||
= Similar Modules = | |||
* Bender modules: [[../Workflow|Workflow]] | |||
* Slicer modules: [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Modules/Editor Editor] | |||
Revision as of 18:49, 11 April 2013
Introduction
The Volume Skinning module is the first step of the skinning process (the second done by the Compute Weights module). Similarly to the traditional skinning technique that assigns a bone for each point of a mesh, Volume Skinning does the assignment for each voxel of a volume. For each voxel of the input volume, the module defines which armature bone influences the most the transform of the voxel when Posing. For example, all the tissue voxels in the lower part of the leg will be assigned the unique id of the tibia bone and the tissue voxels of the upper part of the leg will be assigned the unique ide of the femur bone. The IDs are the indexes of the bones in the armature. The module attempts to find the best bone/voxel pair, however it is not perfect. Manual edition of the skinned volume is likely to be needed. Such edition can be done using the Editor module. Sometimes, a voxel transform might be influenced by more than 1 bone (typically 2). This is the case in the joint's areas (e.g. voxels in the knee area). The transform needs to be a weighted combination of multiple bone transforms (e.g. femur bone + tibia bone). The computation of the weights is done by the Compute Weights module.
Details
Author: Yuanxin Liu, Kitware
Contributor #1: Johan Andruejol, Kitware
Contributor #2: Julien finet, Kitware
Acknowledgements: This work is supported by the Air Force Research Laboratories.
Contact: Julien Finet
Use Cases
Skinned volume and its corresponding model with the armature overlayed.
Volume Skinning in the Workflow after execution
Left: Visibleman labelmap, Center: Skinned volume, Right: Manually edited
