2014 Winter Project Week:IntegrationOfContourObject - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T17:37:24Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Pinter at 18:08, 9 January 2014

2014-01-09T18:08:47Z

Pinter: /* Project Description */

2014-01-08T23:33:49Z

Project Description

Pinter: Link to source code

2014-01-06T22:25:45Z

Link to source code

Pinter at 16:57, 6 January 2014

2014-01-06T16:57:39Z

Pinter at 16:54, 6 January 2014

2014-01-06T16:54:57Z

Pinter: /* Reference */

2013-12-30T01:08:47Z

Reference

Pieper: /* Project Description */

2013-12-20T16:05:15Z

Project Description

Pinter: Page created

2013-11-27T15:55:31Z

Page created

New page

__NOTOC__
<gallery>
Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
Image:SlicerRT_ContourRepresentations.png|Contour representations stored in the Contour object
</gallery>

==Key Investigators==
* Queen's: Csaba Pinter, Andras Lasso
* Isomics: Steve Pieper
* ???

==Project Description==

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Objective</h3>
Handling of contours is a quite common task, however, the current tools are not optimal in doing it conveniently and correctly. The shortcomings are:
* The representations are not bound together, only the name chosen by the users may indicate that they represent the same contour
* Interaction-heavy conversion from one representation to another
* Difficult conversion of multiple contours
* Ensuring the same color is not trivial

[http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Modules/Contours SlicerRT provides a Contour MRML object and module] for quite some time, and it proved really useful. As the notion of contours loaded in one representation and being required for processing in another is not an RT-specific thing, we propose integration of this Contour object in the Slicer core to benefit others working with contours. The currently supported contour representations are:
* Ribbon: Directly created from the 2D planar contours found in DICOM
* Labelmap: Common labelmap object with 0 as a background and a unique (in context, such as an RT structure set) foreground index; The color is provided by a color table automatically generated from the colors found in the DICOM context (RTSS)
* Closed surface model: Nice model, mainly for visualization
The features provided by the Contour MRML object:
* Automatic conversion: if the programmer requests a representation and it doesn't exist, it is automatically converted
* Automatic transforming of all representations if one is transformed
* Invalidate other representations when one is changed (e.g. labelmap edited in Editor)
Features of the Contours module:
* Bulk conversion of structure set
* Set conversion options: reference volume (automatically selected if DICOM provides one), oversampling factor, target reduction factor

</div>
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Approach, Plan</h3>
* Explore all possible
** Input types (DICOM RTSS, Segmentation Object, etc.)
** Use cases
* Discuss how the new Contour object can co-exist with the current set of tools
** Possible merging of those?
* Correct way of implementation: storage node, displayable manager etc.

</div>
<div style="width: 27%; float: left; padding-right: 3%;">
<h3>Progress</h3>
*
</div>
== Reference ==
* [[2013_Summer_Project_Week:Patient_hierarchy|Summer Project Week page]]

@@ Line 49: / Line 49: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Progress</h3>
-* Presented the idea in meetings (Steve, Alex)
+* Presented the idea in meetings (Steve, Alex, Jayashree, Andriy)
 * The Contour object looks useful and convenient, integrating in the core is desirable
 ** Redundant modules

← Older revision		Revision as of 22:25, 6 January 2014
Line 56:		Line 56:
	** Related ticket: [https://www.assembla.com/spaces/slicerrt/tickets/407#/activity/ticket: #407]		** Related ticket: [https://www.assembla.com/spaces/slicerrt/tickets/407#/activity/ticket: #407]
	* Contours CLI integration SlicerRT ticket: [https://www.assembla.com/spaces/slicerrt/tickets/165 #165]		* Contours CLI integration SlicerRT ticket: [https://www.assembla.com/spaces/slicerrt/tickets/165 #165]
		+	* Contours module [https://subversion.assembla.com/svn/slicerrt/trunk/SlicerRt/src/Contours/ source code] (module UI, Contours MRML, conversion utilities, Subject hierarchy plugin)

← Older revision		Revision as of 01:08, 30 December 2013
Line 52:		Line 52:

	== Reference ==		== Reference ==
−	* [[~~2013_Summer_Project_Week~~:~~Patient_hierarchy\|Summer Project Week page~~]]	+	* Contours DisplayableManager and StorageNode SlicerRT ticket: [https://www.assembla.com/spaces/slicerrt/tickets/446#/activity/ticket: #446]
		+	** Related ticket: [https://www.assembla.com/spaces/slicerrt/tickets/407#/activity/ticket: #407]
		+	* Contours CLI integration SlicerRT ticket: [https://www.assembla.com/spaces/slicerrt/tickets/165 #165]

@@ Line 22: / Line 22: @@
 * Ensuring the same color is not trivial
-[http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Modules/Contours SlicerRT provides a Contour MRML object and module] for quite some time, and it proved really useful. As the notion of contours loaded in one representation and being required for processing in another is not an RT-specific thing, we propose integration of this Contour object in the Slicer core to benefit others working with contours. The currently supported contour representations are:
+[https://www.slicer.org/wiki/Documentation/Nightly/Modules/Contours SlicerRT provides a Contour MRML object and module] for quite some time, and it proved really useful. As the notion of contours loaded in one representation and being required for processing in another is not an RT-specific thing, we propose integration of this Contour object in the Slicer core to benefit others working with contours. The currently supported contour representations are:
 * Ribbon: Directly created from the 2D planar contours found in DICOM
 * Labelmap: Common labelmap object with 0 as a background and a unique (in context, such as an RT structure set) foreground index; The color is provided by a color table automatically generated from the colors found in the DICOM context (RTSS)

@@ Line 3: / Line 3: @@
 Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
 Image:SlicerRT_ContourRepresentations.png|Contour representations stored in the Contour object
 </gallery>

@@ Line 8: / Line 8: @@
 * Queen's: Csaba Pinter, Andras Lasso
 * Isomics: Steve Pieper
-* ???
+* Segmentation object project participants?
 ==Project Description==

@@ Line 43: / Line 43: @@
 ** Possible merging of those?
 * Correct way of implementation: storage node, displayable manager etc.
 </div>
@@ Line 49: / Line 50: @@
+*
 </div>
 == Reference ==
 * [[2013_Summer_Project_Week:Patient_hierarchy|Summer Project Week page]]