Difference between revisions of "2012 Summer Project Week:Reporting"

From NAMIC Wiki
Jump to: navigation, search
 
(8 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
<gallery>
 
<gallery>
 
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]]
 
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]]
 +
Image:Slicer4_Reporting_GUI.png|Reporting module GUI
 +
Image:Slicer4_Reporting_extension.png|Reporting extension (do not try it yet! :)
 
</gallery>
 
</gallery>
  
Line 7: Line 9:
 
* BWH: Andrey Fedorov, Nicole Aucoin, Steve Pieper, Ron Kikinis, Fiona Fennessy
 
* BWH: Andrey Fedorov, Nicole Aucoin, Steve Pieper, Ron Kikinis, Fiona Fennessy
 
* Northwestern U: Pat Mongklowat
 
* Northwestern U: Pat Mongklowat
 +
* Kitware: JC
  
 
<div style="margin: 20px;">
 
<div style="margin: 20px;">
Line 28: Line 31:
 
* consider integrating Reporting as an extension
 
* consider integrating Reporting as an extension
 
* discuss how support of DICOM SEG should be integrated into Slicer
 
* discuss how support of DICOM SEG should be integrated into Slicer
 +
* connection/extension of DICOM SEG and the lookup table concept of Slicer
 
</div>
 
</div>
  
Line 33: Line 37:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
 +
 +
* we worked on integrating the Reporting module as a Slicer extension
 +
** work is taking place in the git branch here: https://github.com/fedorov/Reporting/tree/extension
 +
** application key has been obtained following the guidelines
 +
** Reporting extension ExperimentalUpload build has been accomplished and the packaged extension has been uploaded: http://slicer.cdash.org/buildSummary.php?buildid=25213
 +
** issue has been identified in testing infrastructure that causes unit test to crash, fixed by JC http://www.na-mic.org/Bug/view.php?id=2248
 +
** it was identified that loading DICOM scalar volumes leads to a crash, preventing the use of Reporting module, bug report submitted: http://www.na-mic.org/Bug/view.php?id=2241
 +
** another related bug submitted: http://www.na-mic.org/Bug/view.php?id=2251
 +
* integration of DICOM SEG support has been discussed as part of DICOM breakout (see notes here: [[2012_Summer_Project_Week_Breakout_Session:Slicer_DICOM]])
 +
* we worked on compiling AIM 3.0 API on Mac, but not succeeded
 +
* discussed with the AIM experts the details of saving annotations: only one annotation and image reference should be saved per AIM file, if the AIM format is to be followed precisely
  
 
</div>
 
</div>

Latest revision as of 15:23, 22 June 2012

Home < 2012 Summer Project Week:Reporting

Key Investigators

  • BWH: Andrey Fedorov, Nicole Aucoin, Steve Pieper, Ron Kikinis, Fiona Fennessy
  • Northwestern U: Pat Mongklowat
  • Kitware: JC

Objective

As part of BWH QIN project, we are working on implementing support for

  • organizing Slicer markup and annotations into hierarchies to maintain their relationship with the original volumes
  • export these hierarchies and Slicer internal data structures into other formats (e.g., AIM)

This development is currently happening within Reporting module (available on github).

Approach, Plan

  • present the capabilities of the Reporting module to the interested groups
  • discuss the missing features and roadmap for future development
  • cross-check with the AIM experts (Pat) that the AIM output is correct
  • discuss the possibility of integrating Reporting module with the native AIM API, which is currently under development by Pat Mongklowat's group
  • consider integrating Reporting as an extension
  • discuss how support of DICOM SEG should be integrated into Slicer
  • connection/extension of DICOM SEG and the lookup table concept of Slicer

Progress

Delivery Mechanism

Reporting module is available as a Slicer4 loadable module, source code available on github: https://github.com/fedorov/Reporting

References