Difference between revisions of "2016 Winter Project Week/Projects/DICOMSegObjIntegration"

From NAMIC Wiki
Jump to: navigation, search
 
(14 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
Image:PW-MIT2016.png|link=2016_Winter_Project_Week#Projects|[[2016_Winter_Project_Week#Projects|Projects List]]
 
Image:PW-MIT2016.png|link=2016_Winter_Project_Week#Projects|[[2016_Winter_Project_Week#Projects|Projects List]]
 
<!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" -->
 
<!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" -->
 +
Image:Segmentations.png
 +
Image:PW-MIT2016-BrainlabChestSegmentationsSlicer.png
 
</gallery>
 
</gallery>
  
 
==Key Investigators==
 
==Key Investigators==
<!-- Add a bulleted list of investigators and their institutions here -->
+
* Kyle Sunderland, Queen's
 +
* Csaba Pinter, Queen's
 +
* Andras Lasso, Queen's
 +
* Andrey Fedorov, BWH
 +
* Steve Pieper, Isomics
  
 
==Project Description==
 
==Project Description==
Line 16: Line 22:
 
|
 
|
 
<!-- Objective bullet points -->
 
<!-- Objective bullet points -->
*
+
* Implement a DICOM plugin that creates Segmentation Nodes using the DICOM Segmentation image import/export code.
 
|
 
|
 
<!-- Approach and Plan bullet points -->
 
<!-- Approach and Plan bullet points -->
*  
+
* DICOM SegObj import/export is already implemented.
 +
* The [http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/Modules/Segmentations Segmentations] infrastructure will soon be integrated into Slicer core.
 +
* Create a Python DICOM plugin to store the information from DICOM segmentations as Segmentation objects.
 
|
 
|
 
<!-- Progress and Next steps bullet points (fill out at the end of project week -->
 
<!-- Progress and Next steps bullet points (fill out at the end of project week -->
*
+
* Importing has been updated to work with Segmentations; it is now possible to load DICOM SEG objects associated with different instances, which was/is not possible with the labelmap/editor based approach
 +
* Exporting of Segmentations to DICOM SEG objects is now implemented.
 
|}
 
|}
  
 
==Background and References==
 
==Background and References==
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 +
 +
[https://github.com/Sunderlandkyl/Reporting Source Code (Reporting Fork)]
 +
 +
[https://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/Reporting Reporting Extension] ([https://github.com/QIICR/Reporting Github])

Latest revision as of 15:04, 8 January 2016

Home < 2016 Winter Project Week < Projects < DICOMSegObjIntegration

Key Investigators

  • Kyle Sunderland, Queen's
  • Csaba Pinter, Queen's
  • Andras Lasso, Queen's
  • Andrey Fedorov, BWH
  • Steve Pieper, Isomics

Project Description

Objective Approach and Plan Progress and Next Steps
  • Implement a DICOM plugin that creates Segmentation Nodes using the DICOM Segmentation image import/export code.
  • DICOM SegObj import/export is already implemented.
  • The Segmentations infrastructure will soon be integrated into Slicer core.
  • Create a Python DICOM plugin to store the information from DICOM segmentations as Segmentation objects.
  • Importing has been updated to work with Segmentations; it is now possible to load DICOM SEG objects associated with different instances, which was/is not possible with the labelmap/editor based approach
  • Exporting of Segmentations to DICOM SEG objects is now implemented.

Background and References

Source Code (Reporting Fork)

Reporting Extension (Github)