<p dir="ltr">Hi Ralf,</p>
<p dir="ltr">Just a word of caution regarding Rob's suggestion of using MRtrix3's fod2metric: if you do want to use it on existing data processed using the current stable release (0.2.x), then you'll need to worry about the change in the SH basis (see for details: <a href="https://github.com/jdtournier/mrtrix3/wiki/Orthonormal-SH-basis">https://github.com/jdtournier/mrtrix3/wiki/Orthonormal-SH-basis</a>).</p>
<p dir="ltr">In general, I'd advise against mixing 0.2.x commands with MRtrix3 commands, unless you have a very good understanding of what the change in SH basis means, and you take great care to keep track of which image was generated using which version. </p>
<p dir="ltr">Cheers,<br>
Donald</p>
<p dir="ltr">--<br>
Dr J-Donald Tournier (PhD)</p>
<p dir="ltr">Senior Lecturer, Biomedical Engineering<br>
Division of Imaging Sciences & Biomedical Engineering<br>
King's College London</p>
<p dir="ltr">A: Department of Perinatal Imaging & Health, 1st Floor South Wing, St Thomas' Hospital, London. SE1 7EH<br>
T: +44 (0)20 7188 7118 ext 53613<br>
W: <a href="http://www.kcl.ac.uk/medicine/research/divisions/imaging/departments/biomedengineering">http://www.kcl.ac.uk/medicine/research/divisions/imaging/departments/biomedengineering</a><br>
</p>
<div class="gmail_quote">On 18 Jun 2014 08:32, "Robert Smith" <<a href="mailto:robert.smith@florey.edu.au">robert.smith@florey.edu.au</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>Hi Ralf,<br><br><br></div>1. A command you definitely want to have a look at in the new MRtrix release is <span style="font-family:courier new,monospace">fod2metric</span>.<br>It performs FOD segmentation as outlined in Appendix 2 of <a href="http://www.sciencedirect.com/science/article/pii/S1053811912011615" target="_blank">this paper</a>, and can output various statistics on the results (see the help file of the command for full details).<br>
</div>It's also a neat way to familiarise yourself with concepts relating to how to deal with multiple fibres per voxel in a context other than tractography; for instance, the <a href="https://github.com/jdtournier/mrtrix3/wiki/Dixels-and-Fixels" target="_blank">terminology</a> you may use in such a context, how to <a href="https://github.com/jdtournier/mrtrix3/wiki/MRtrix-Sparse-image-formats-(.msf-.msh)" target="_blank">store such data</a>, and how to <a href="http://www.sciencedirect.com/science/article/pii/S1053811911012092" target="_blank">perform</a> <a href="http://www.ismrm.org/13/session83.htm" target="_blank">statistical</a> <a href="http://www.ismrm.org/14/program_files/Session57.htm" target="_blank">comparisons</a>...<br>
<div> <br><br></div><div>2. Regarding the image overlay, it's important to understand that the viewer does not perform an explicit image registration step between images when you load one of them using the overlay tool. If you want the images to overlap, then most likely some explicit image registration step will first be required. If however we assume that such a registration step has been performed, the second important concept to understand is that two images can be aligned with one another in <i>real space</i>, even if they do not possess the same image transform or voxel sizes.<br>
<br></div><div>So let's imagine that you've loaded your MPRAGE in mrview; you can think of the 'camera' in the viewer being a 2D plane that is 'snapped' to whatever alignment the voxel grid of that MPrage happens to have. You then load your DWI using the overlay tool. Now the DWI is drawn over the top of the MPRAGE, based on the position of the 'camera', and the image transform of the DWI. The fact that the DWI doesn't have the same image transform and voxel size as the MPRAGE (i.e. the image data have not bee <i>re-gridded</i>) doesn't matter; it's drawn over the top of the image you're looking at using interpolation. This argument still holds even if the 'camera' is not locked to the underlying MPRAGE (i.e. you've turned off the 'lock to image axes' option), in which case the 'camera' defines a plane through space, and <i>both images</i> are drawn upon this plane using interpolation.<br>
<br></div><div>Now imagine that you have <i>not</i> performed an image registration step first, and the subject moved significantly between the two acquisitions. Now when you overlay the DWI, not only do the image transforms and voxel sizes differ, but the actual <i>position of the brain in real space</i> also differs, i.e. the image information from the two images doesn't overlap, no matter how you look at them.<br>
<br></div><div>The distinction between image registration, image re-gridding / re-sampling, and image overlay, is very important to ensure that such questions are interpreted correctly.<br><br></div><div>Best regards<br>
Rob</div>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><br>--<br><br><span style="color:rgb(255,102,0)"><b>Robert Smith, Ph.D</b><br>Research Officer, Imaging Division</span><br><br>The Florey Institute of Neuroscience and Mental Health<br>
Melbourne Brain Centre - Austin Campus<br>245 Burgundy Street<br>Heidelberg Vic 3084<br>Ph: +61 3 9035 7128<br>Fax: +61 3 9035 7301<br><a href="http://www.florey.edu.au/" target="_blank">www.florey.edu.au</a><br></div></div>
<br><br><div class="gmail_quote">On Tue, Jun 17, 2014 at 6:27 PM, Luetzkendorf, Ralf <span dir="ltr"><<a href="mailto:Ralf.Luetzkendorf@med.ovgu.de" target="_blank">Ralf.Luetzkendorf@med.ovgu.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Donald,<br>
<br>
thanks for the quick answer.<br>
<br>
1. What I meant with 1. was, if I have one ODF in my image, can I get some values for that ODF, like:<br>
- how many directions it has and how strong<br>
- angle<br>
- vector<br>
or something. So that I have something for a statistics or to compare to subjects in that voxel or the same subject with different measurment parameters or different MR Scanners.<br>
<br>
Im not sure if "find_SH_peaks" does that. I will test it.<br>
<br>
2. If I open MPRage with MRview and overlay DWI and they have not the same resolution. Does it register the DWI to the MPRage or the MPrage to the DWI?<br>
<br>
Thanks for the help and sorry for the inexplicit questions,<br>
<div><br>
Ralf<br>
<br>
<br>
+++++++++++++++++++++++++++++++++++++++++++++++<br>
Ralf Lützkendorf<br>
Department for Biometry and Medical Informatics<br>
University of Magdeburg, Germany<br>
phone: <a href="tel:%2B49%20391%2067%2013546" value="+493916713546" target="_blank">+49 391 67 13546</a><br>
fax: <a href="tel:%2B49%20391%2067%2013536" value="+493916713536" target="_blank">+49 391 67 13536</a><br>
<br>
________________________________<br>
</div>Von: Donald Tournier [<a href="mailto:jdtournier@gmail.com" target="_blank">jdtournier@gmail.com</a>]<br>
Gesendet: Montag, 16. Juni 2014 19:29<br>
An: Lützkendorf, Ralf<br>
Cc: mrtrix mailinglist<br>
Betreff: Re: [Mrtrix-discussion] CSD<br>
<div><div><br>
<br>
Hi Ralf,<br>
<br>
I'm assuming you're talking about the stable version of MRtrix (the 0.2.x branch)? If so:<br>
<br>
> 1. Is there a way to have a selected ODF in values, angles or something? Would be interesting to see or compare!<br>
><br>
<br>
I'm not sure what you mean by that exactly. You can use find_SH_peaks to get the vectors corresponding to the fODF peaks (scaled by their amplitude), maybe this is what you're after?<br>
<br>
> 2. What does MRViewer do if you overlay DWI over anatomie? Is it interpolating the DWI or the Anatomie or something in between?<br>
<br>
Both images are interpolated, unless you explicitly turn it off AND 'lock to image axes' is on (the default), in which case the main image is not interpolated. The overlay image is always interpolated, but if both images align exactly, then the interpolation has negligible effect.<br>
<br>
> 3. Is there a way to do the TDI for the Gray matter? I set the thresgold for the FA Map very low, but its not enough I guess!<br>
<br>
There is no FA threshold with streamtrack unless you use the DT_STREAM algorithm, which isn't recommended for TDI (actually, it isn't recommended under any circumstances). If you set the cutoff sufficiently low, you should be able to track through these regions, although how good the results are will depend very much on how good your data are, these regions are really noisy at best... So not too sure why you would have trouble with that, unless 'setting the FA threshold' is a different operation from what I think it is... ?<br>
<br>
Cheers,<br>
Donald a<br>
<br>
><br>
><br>
> Thanks for the help,<br>
><br>
> Ralf<br>
><br>
><br>
><br>
> +++++++++++++++++++++++++++++++++++++++++++++++<br>
> Ralf Lützkendorf<br>
> Department for Biometry and Medical Informatics<br>
> University of Magdeburg, Germany<br>
> phone: <a href="tel:%2B49%20391%2067%2013546" value="+493916713546" target="_blank">+49 391 67 13546</a><br>
> fax: <a href="tel:%2B49%20391%2067%2013536" value="+493916713536" target="_blank">+49 391 67 13536</a><br>
> _______________________________________________<br>
> Mrtrix-discussion mailing list<br>
</div></div>> <a href="mailto:Mrtrix-discussion@www.nitrc.org" target="_blank">Mrtrix-discussion@www.nitrc.org</a><mailto:<a href="mailto:Mrtrix-discussion@www.nitrc.org" target="_blank">Mrtrix-discussion@www.nitrc.org</a>><br>
> <a href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" target="_blank">http://www.nitrc.org/mailman/listinfo/mrtrix-discussion</a><br>
<div><div>_______________________________________________<br>
Mrtrix-discussion mailing list<br>
<a href="mailto:Mrtrix-discussion@www.nitrc.org" target="_blank">Mrtrix-discussion@www.nitrc.org</a><br>
<a href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" target="_blank">http://www.nitrc.org/mailman/listinfo/mrtrix-discussion</a><br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>
Mrtrix-discussion mailing list<br>
<a href="mailto:Mrtrix-discussion@www.nitrc.org">Mrtrix-discussion@www.nitrc.org</a><br>
<a href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" target="_blank">http://www.nitrc.org/mailman/listinfo/mrtrix-discussion</a><br>
<br></blockquote></div>