MRIimage: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
Jadrian Miles (talk | contribs)
No edit summary
Jadrian Miles (talk | contribs)
No edit summary
Line 1: Line 1:
{{stub}}
{{stub}}
MRIimage is our in-house format for storing MRI data and is used as the underlying file format for most of what we do in the [[Diffusion MRI]] project.  It is manipulated by the <code>gg/mri_g++-*</code> library and its header is <code>&lt;gg/mri/image.H&gt;</code>.
MRIimage is our in-house format for storing MRI data and is used as the underlying file format for most of what we do in the [[Diffusion MRI]] project.  It is manipulated by the <code>gg/mri_g++-*</code> library and its header is <code>&lt;gg/mri/image.H&gt;</code>. A number of [[diffusion MRI Matlab scripts|Matlab scripts]] have also been written to interact with this file format.
 
In MRIimage, an image volume is represented by a directory containing a number of files:
* '''resolution''': a text file indicating the resolution of the image in voxels.  Images are 4-D; a single DWI will have resolution <tt>1</tt> in the fourth dimension, while a DTI will have resolution <tt>6</tt>.
* '''i.''n''''': a raw 2-D image slice, stored in fixed-point format as little-endian <tt>uint16</tt>.  ''n'' corresponds to the X-Y slice number, which increases sequentially as the index in the fourth dimension increases, and is formatted as a string in the filename like <code>printf("%03d",n)</code>; hence numbers <1000 are zero-padded to three digits.  Since the fourth dimension is of unit size in a DWI, ''n'' increases sequentially as the index in Z increases.  For a DTI, however:
** <tt>i.001</tt> stores the slice for Z=0 and the first tensor component
** <tt>i.002</tt> stores the slice for Z=0 and the second tensor component
** ...
** <tt>i.006</tt> stores the slice for Z=0 and the sixth tensor component
** <tt>i.007</tt> stores the slice for Z=1 and the first tensor component
** ...
** <tt>i.012</tt> stores the slice for Z=1 and the sixth tensor component
** ..
** <tt>i.''n''</tt> stores the slice for <math>Z = \lfloor (n-1)/6 \rfloor</math> and the <math>((n-1) \mod 6) + 1</math>-th tensor component
* '''vsize''': a text file indicating the voxel size in millimeters
* '''parameters''': a text file indicating the fixed-point parameters (<tt>scaleIntensity</tt> and <tt>offsetIntensity</tt>) and imaging parameters such as TR, TE, and data-to-lab-frame translation
 


[[Category:Diffusion MRI]][[Category:File Formats]]
[[Category:Diffusion MRI]][[Category:File Formats]]

Revision as of 23:07, 6 July 2009

MRIimage is our in-house format for storing MRI data and is used as the underlying file format for most of what we do in the Diffusion MRI project. It is manipulated by the gg/mri_g++-* library and its header is <gg/mri/image.H>. A number of Matlab scripts have also been written to interact with this file format.

In MRIimage, an image volume is represented by a directory containing a number of files:

  • resolution: a text file indicating the resolution of the image in voxels. Images are 4-D; a single DWI will have resolution 1 in the fourth dimension, while a DTI will have resolution 6.
  • i.n: a raw 2-D image slice, stored in fixed-point format as little-endian uint16. n corresponds to the X-Y slice number, which increases sequentially as the index in the fourth dimension increases, and is formatted as a string in the filename like printf("%03d",n); hence numbers <1000 are zero-padded to three digits. Since the fourth dimension is of unit size in a DWI, n increases sequentially as the index in Z increases. For a DTI, however:
    • i.001 stores the slice for Z=0 and the first tensor component
    • i.002 stores the slice for Z=0 and the second tensor component
    • ...
    • i.006 stores the slice for Z=0 and the sixth tensor component
    • i.007 stores the slice for Z=1 and the first tensor component
    • ...
    • i.012 stores the slice for Z=1 and the sixth tensor component
    • ..
    • i.n stores the slice for Z=(n1)/6 and the ((n1)mod6)+1-th tensor component
  • vsize: a text file indicating the voxel size in millimeters
  • parameters: a text file indicating the fixed-point parameters (scaleIntensity and offsetIntensity) and imaging parameters such as TR, TE, and data-to-lab-frame translation