Diffusion Processing Pipeline/bugs and feature requests: 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:
== Bugs ==
* <tt>mrifilt3</tt>, <tt>mricrop</tt>, <tt>mrisubset</tt>, and possibly others mangle the parameters file.  In particular, if you operate on a DWI, the output won't have the b matrix recorded.  Also the <tt>MRISpaceShift</tt> just gets clobbered to 0 0 0.
* <tt>mrifilt3</tt>, <tt>mricrop</tt>, <tt>mrisubset</tt>, and possibly others mangle the parameters file.  In particular, if you operate on a DWI, the output won't have the b matrix recorded.  Also the <tt>MRISpaceShift</tt> just gets clobbered to 0 0 0.
** A workaround right now for the b matrix, TR, and TE is <pre>grep "^b\|e0" $src/parameters >> $dest/parameters</pre>
** A workaround right now for the b matrix, TR, and TE is <pre>grep "^b\|e0" $src/parameters >> $dest/parameters</pre>
* Streamtube generation gets slower and slower as the program runs.  What's going on?  Is it running out of memory, reading inefficiently through a big file, doing something probabilistic that gets less likely the more tubes there are?  We need a speedup!
* Streamtube generation gets slower and slower as the program runs.  What's going on?  Is it running out of memory, reading inefficiently through a big file, doing something probabilistic that gets less likely the more tubes there are?  We need a speedup!
== Feature Requests ==
* Most operations, including tensor fitting and tube generation, are highly parallelizable.  It'd be great if we could throw them on the department's compute grid.
* Most operations, including tensor fitting and tube generation, are highly parallelizable.  It'd be great if we could throw them on the department's compute grid.


[[Category:Diffusion MRI]][[Category:Bug Tracking Pages]]
[[Category:Diffusion MRI]][[Category:Bug Tracking Pages]]

Revision as of 22:00, 17 November 2008

Bugs

  • mrifilt3, mricrop, mrisubset, and possibly others mangle the parameters file. In particular, if you operate on a DWI, the output won't have the b matrix recorded. Also the MRISpaceShift just gets clobbered to 0 0 0.
    • A workaround right now for the b matrix, TR, and TE is
      grep "^b\|e0" $src/parameters >> $dest/parameters
  • Streamtube generation gets slower and slower as the program runs. What's going on? Is it running out of memory, reading inefficiently through a big file, doing something probabilistic that gets less likely the more tubes there are? We need a speedup!

Feature Requests

  • Most operations, including tensor fitting and tube generation, are highly parallelizable. It'd be great if we could throw them on the department's compute grid.