Difference between revisions of "2010 WinterProject Week MRSIModule"

From NAMIC Wiki
Jump to: navigation, search
Line 31: Line 31:
 
We adapted the current MRSI processing routine to be separable into several sub-routines (see Figure), each of which to be usable as external CLI module and depending on few (or single) external libraries only.  
 
We adapted the current MRSI processing routine to be separable into several sub-routines (see Figure), each of which to be usable as external CLI module and depending on few (or single) external libraries only.  
  
We worked towards integrating an exemplary subroutine -- together with its external library -- as an external CLI module into Slicer potentially to be distributed as a Slicer extension.
+
We worked towards integrating an exemplary subroutine -- together with its external library -- as an external CLI module, and potentially to be distributed as a Slicer extension.
  
 
</div>
 
</div>

Revision as of 15:27, 8 January 2010

Home < 2010 WinterProject Week MRSIModule

Key Investigators

  • MIT: Bjoern Menze, Polina Golland


Objective

Magnetic resonance spectroscopic imaging (MRSI) is a non-invasive diagnostic method used to determine the relative abundance of specific metabolites at arbitrary locations in vivo. Certain diseases -- such as tumors in brain, breast and prostate -- can be can be associated with characteristic changes in the metabolic level.

The objective of the current project is to develop a module proving the means for the processing and visualization of MRSI -- and thus for a joint analysis of magnetic resonance spectroscopic images together with other imaging modalities -- in Slicer.

Approach, Plan

Spectral fitting routines have been implemented, using a HSVD filter for water peak removal and baseline estimation, and a constrained non-linear least squares optimization for the fit of the resonance line models. Current fitting routines require, however, several external software libraries not to be distributed, installed and used easily.

We want to find directions for either replacing these third-party libraries -- e.g. by using standard optimization routines from Python being available in Slicer -- or for making them easily available to the user of the module.

Progress

We adapted the current MRSI processing routine to be separable into several sub-routines (see Figure), each of which to be usable as external CLI module and depending on few (or single) external libraries only.

We worked towards integrating an exemplary subroutine -- together with its external library -- as an external CLI module, and potentially to be distributed as a Slicer extension.