Diffusion Processing Pipeline/bugs and feature requests: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
== Feature Requests == | == 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. | ||
* Rename batch scripts to get rid of ambiguous terms like "process". <tt>processNiftiDwis.py</tt>, for example, could be changed to <tt>nifti2mriimage_batch.py</tt>. | |||
[[Category:Diffusion MRI]][[Category:Bug Tracking Pages]] | [[Category:Diffusion MRI]][[Category:Bug Tracking Pages]] | ||
Revision as of 17:22, 12 March 2009
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
- A workaround right now for the b matrix, TR, and TE is
- 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.
- Rename batch scripts to get rid of ambiguous terms like "process". processNiftiDwis.py, for example, could be changed to nifti2mriimage_batch.py.