Contours

Laboratory for Percutaneous Surgery – Copyright © Queen’s University, 2013

- 2 -

• Some discussion points from winter achieved– Refactor to single node, storage node, display node

• Some discussion points not achieved– Redundant modules– Core integration

Winter 2014

Laboratory for Percutaneous Surgery – Copyright © Queen’s University, 2013

- 3 -

• 3 Nodes -> 1 Node• vtkMRMLContourNode is now

– vtkImageData*– vtkPolyData* x 2 (under design to be reduced to 1)– ImageData will hopefully be used as an editable

representation in the Editor module

• vtkMRMLContourStorageNode as expected– qSlicerContoursReader

Summary of Changes (con’t)

Laboratory for Percutaneous Surgery – Copyright © Queen’s University, 2013

- 4 -

• vtkMRMLContourModelDisplayNode– Child of vtkMRMLModelDisplayNode– Essentially empty, but RTTI information is used

• Accessory fuctions to create from and extract to labelmap (and other smaller functions)

Summary of Changes (con’t)

Laboratory for Percutaneous Surgery – Copyright © Queen’s University, 2013

- 5 -

• Structure representation?– Compare to labelmap

• Pros:– Mesh representation can hold multiple structures per mesh without too

much additional memory– Algorithms can convert to labelmap on the fly, allow modification

» At the moment not clear how to return it to mesh, will this produce a satisfactory result?

• Cons:– Work required? Current solution works

Purpose of Contour

Laboratory for Percutaneous Surgery – Copyright © Queen’s University, 2013

- 6 -

• Requested features– Edit contour from Editor module (Rankin)– Ensure single data origin (mesh? Points?) (Rankin)

• After editing contour, propagate changes to origin

– <your feature here>

• Core integration?– Necessary for some features– Stabilization and cleanup required

Going Forward