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

From NAMIC Wiki
Jump to: navigation, search
Line 40: Line 40:
 
** application key has been obtained following the guidelines
 
** 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
 
** Reporting extension ExperimentalUpload build has been accomplished and the packaged extension has been uploaded: http://slicer.cdash.org/buildSummary.php?buildid=25213
 +
** it was identified that loading DICOM scalar volumes leads to a crash, preventing the use of Reporting module, but submitted: http://www.na-mic.org/Bug/view.php?id=2241
 
** issue has been identified in testing infrastructure that causes unit test to crash, JC is working on it
 
** issue has been identified in testing infrastructure that causes unit test to crash, JC is working on it
 
* integration of DICOM SEG support has been discussed as part of DICOM breakout (see notes here: [[2012_Summer_Project_Week_Breakout_Session:Slicer_DICOM]])
 
* integration of DICOM SEG support has been discussed as part of DICOM breakout (see notes here: [[2012_Summer_Project_Week_Breakout_Session:Slicer_DICOM]])

Revision as of 23:55, 21 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

  • we worked on integrating the Reporting module as a Slicer extension
  • 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

Delivery Mechanism

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

References