Difference between revisions of "2014 Winter Project Week:Constrain Fiducial along Suface"
From NAMIC Wiki
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2014.png|Projects List </gallery> ==Key Investigators== * BWH: Nicole Aucoin * University of Michigan: Vini…') |
|||
| Line 23: | Line 23: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * During the talk with Nicole Aucoin we walked through the code already written in Slicer3, the Measurements module. She showed how it was done and what would be needed to have it implemented into Slicer4. |
| + | * Things to be done: | ||
| + | ** Add the model ID into vtkMRMLMarkupsNode() | ||
| + | ** The vtkPolygonalSurfacePointPlacer needs to add the markupsDisplayableManager3D | ||
| + | ** Get the vtkProp *prop can be trick | ||
| + | ** There's already a widget in Slicer3, inside vtkSlicerWidgetClass.cxx has the vtkPolygonalSurfacePointPlacer, so the markups will be managing it. | ||
</div> | </div> | ||
Latest revision as of 16:09, 10 January 2014
Home < 2014 Winter Project Week:Constrain Fiducial along Suface
Key Investigators
- BWH: Nicole Aucoin
- University of Michigan: Vinicius Boen
Project Description
Objective
- Create a development plan for constrain a fiducial to move only along a surface for Slicer4.
Approach, Plan
- Explorer how it was done for Slicer3 in the Measurements module and the best way it could be done in order to have it implemented for Slicer4.
Progress
- During the talk with Nicole Aucoin we walked through the code already written in Slicer3, the Measurements module. She showed how it was done and what would be needed to have it implemented into Slicer4.
- Things to be done:
- Add the model ID into vtkMRMLMarkupsNode()
- The vtkPolygonalSurfacePointPlacer needs to add the markupsDisplayableManager3D
- Get the vtkProp *prop can be trick
- There's already a widget in Slicer3, inside vtkSlicerWidgetClass.cxx has the vtkPolygonalSurfacePointPlacer, so the markups will be managing it.
