Difference between revisions of "2017 Winter Project Week/GeodesicSegmentationandLungtumorAnalysis"

From NAMIC Wiki
Jump to: navigation, search
 
(7 intermediate revisions by the same user not shown)
Line 6: Line 6:
  
 
==Key Investigators==
 
==Key Investigators==
* Sarthak.P, CBICA, UPenn
+
* Patmaa Sridharan - UPenn CBICA
* Saima.R, CBICA, UPenn
+
* Andras Lasso
* Ratheesh.K CBICA, UPenn
+
* Louise Oram
* Patmaa.S CBICA,UPenn
 
* Mark.B , CBICA, UPenn
 
* Ragini.V CBICA, UPenn
 
* Despina k, CBICA, UPenn
 
* Yong F, CBICA, UPenn
 
* Christos.D, CBICA, UPenn
 
  
 
==Project Description==
 
==Project Description==
Line 26: Line 20:
 
<!-- Objective bullet points -->
 
<!-- Objective bullet points -->
  
Integrate two algorthims with slicer and also focus on getting some applications available in Slicer to be callable from CapTk(out internal tool).
+
Integrate two applications listed below with slicer and also focus on interaction between Slicer and CAPTk(our internal tool)
 
* Geodesic Segmentation
 
* Geodesic Segmentation
 
   A generic segmentation algorithm that uses geodesic distances.
 
   A generic segmentation algorithm that uses geodesic distances.
Line 34: Line 28:
 
|
 
|
 
<!-- Approach and Plan bullet points -->
 
<!-- Approach and Plan bullet points -->
*Do a code level integration of this application with Slicer
 
*Enabling Slicer's GUI to provide seed point intializations and to display the algorithm output.
 
  
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
+
*Analyze the compatibility between the dependencies of our code with that of Slicer and solve it for smooth interaction with our application.
*
+
*Enabling Slicer's GUI to provide seed point initialization required for our application.
 +
*Do a code level integration of geodesic segmentation and SBRT with Slicer.
 +
*Investigate on possibility of calling Slicer from CapTk and vice-versa by using pre-populated project files.
 +
|
 +
<!-- Progress and Next steps bullet points -->
 +
* Had discussions on how to get CAPTk and Slicer communicate and get to use some of the applications of Slicer from CapTk
 +
* On process of getting geodesic segmentation into a Slicer plugin.
 +
* Next Steps
 +
* Finish the plugin and submit it for adding as a module
 +
* Finish the OpenIGT linking to CAPTk to enable both applications communicate
 +
 
 
|}
 
|}
  
 
==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 -->

Latest revision as of 18:56, 13 January 2017

Home < 2017 Winter Project Week < GeodesicSegmentationandLungtumorAnalysis

Key Investigators

  • Patmaa Sridharan - UPenn CBICA
  • Andras Lasso
  • Louise Oram

Project Description

Objective Approach and Plan Progress and Next Steps

Integrate two applications listed below with slicer and also focus on interaction between Slicer and CAPTk(our internal tool)

  • Geodesic Segmentation
  A generic segmentation algorithm that uses geodesic distances.
  • SBRT Lung Tumor segmentation and Analysis
 Segmentation of lung tumor from multimodal images- CT and PET using initial seed points. Analyze the segmented region using texture features and predict the nodal failure in lung.
  • Analyze the compatibility between the dependencies of our code with that of Slicer and solve it for smooth interaction with our application.
  • Enabling Slicer's GUI to provide seed point initialization required for our application.
  • Do a code level integration of geodesic segmentation and SBRT with Slicer.
  • Investigate on possibility of calling Slicer from CapTk and vice-versa by using pre-populated project files.
  • Had discussions on how to get CAPTk and Slicer communicate and get to use some of the applications of Slicer from CapTk
  • On process of getting geodesic segmentation into a Slicer plugin.
  • Next Steps
  • Finish the plugin and submit it for adding as a module
  • Finish the OpenIGT linking to CAPTk to enable both applications communicate

Background and References