Difference between revisions of "2011 Winter Project Week:SPECTRE Integration"

From NAMIC Wiki
Jump to: navigation, search
Line 54: Line 54:
 
<h3>Progress</h3>
 
<h3>Progress</h3>
  
 +
<ul>
 +
<li>Y flip
 +
<ul>
 +
<li>Atlas file OAS1_0001_MR1_original.hdr & .img loaded into Slicer using Add Data. Saved in .nhdr nrrd format, .nhdr contains:
 +
<pre>space: left-posterior-superior
 +
sizes: 176 208 176
 +
space directions: (1,0,0) (0,-1,0) (0,0,1)
 +
space origin: (0,0,0)</pre>
 +
<li>Loading the .nhdr file back into Slicer, volume aligns with .hdr/.img
 +
<li>Turning off deleting intermediate files for SPECTRE:
 +
  [$::slicer3::CommandLineModuleGUI_SPECTRE_2009 GetLogic] DeleteTemporaryFilesOff
 +
<li>Running the algorithm, generating only stripped image. unu head on input image BJAIF_vtkMRMLScalarVolumeNodeB.nrrd:
 +
<pre>space: left-posterior-superior
 +
sizes: 176 208 176
 +
space directions: (1,0,0) (0,-1,0) (0,0,1)
 +
space origin: (0,0,0)
 +
</pre>
 +
<li>unu head on output stripped image BJAIF_vtkMRMLScalarVolumeNodeD.nrrd:
 +
<pre>
  
 +
</pre>
 +
</ul>
 +
</ul>
  
 
</div>
 
</div>

Revision as of 18:10, 29 December 2010

Home < 2011 Winter Project Week:SPECTRE Integration

Key Investigators

  • BWH: Nicole Aucoin
  • JHU: Min Chen

Objective

To advance the integration of the Java based SPECTRE algorithm into Slicer3 (and Slicer4), to find validation data sets.



Approach, Plan

Our approach is to fine tune the integration for Slicer3, write a python wrapping script for Slicer4, fine tune the ACPC algorithm. The main challenge to this approach is coordinate system transforms.

Our plan for the project week is:

  • Add a memory argument to the SPECTRE xml and use it to set Java heap sizes
  • Fine tune the Java handling in Slicer3 to fail gracefully if Java is not available on a build machine
  • Debug the ACPC algorithm in SPECTRE
    • Add a transform output to SPECTRE
  • Debug y flip on reading in output images into Slicer
  • Find collaborators with segemented data sets for the validation portion of our project. Ron has suggested talking with:
    • Sylvain Bioux
    • Hans Johnson
  • Write a python wrapper so we can integrate SPECTRE into Slicer4
  • Work on documentation so that the manual steps are as clear as possible
  • Remove the requirement to have to run MIPAV before running the SPECTRE extension in Slicer.
  • Set volume types in SPECTRE outputs

Progress

  • Y flip
    • Atlas file OAS1_0001_MR1_original.hdr & .img loaded into Slicer using Add Data. Saved in .nhdr nrrd format, .nhdr contains: 
      space: left-posterior-superior
sizes: 176 208 176
space directions: (1,0,0) (0,-1,0) (0,0,1)
space origin: (0,0,0)
    • Loading the .nhdr file back into Slicer, volume aligns with .hdr/.img
    • Turning off deleting intermediate files for SPECTRE: [$::slicer3::CommandLineModuleGUI_SPECTRE_2009 GetLogic] DeleteTemporaryFilesOff
    • Running the algorithm, generating only stripped image. unu head on input image BJAIF_vtkMRMLScalarVolumeNodeB.nrrd: 
      space: left-posterior-superior
sizes: 176 208 176
space directions: (1,0,0) (0,-1,0) (0,0,1)
space origin: (0,0,0)
    • unu head on output stripped image BJAIF_vtkMRMLScalarVolumeNodeD.nrrd:

Delivery Mechanism

This work will be delivered to the NA-MIC Kit as a

  1. ITK Module
  2. Slicer Module
    1. Built-in
    2. Extension -- commandline YES
    3. Extension -- loadable


References

Retrieved from "https://www.na-mic.org/w/index.php?title=2011_Winter_Project_Week:SPECTRE_Integration&oldid=62715"