[Camino-users] selectshells and Restore issue for data analysis

Ajay Kurani dr.ajay.kurani at gmail.com
Sat Jun 10 12:45:02 PDT 2017


Hi Camino Experts,
   I am new to the software and have one or two questions related to errors
I received in processing.

1) selectshells - in the web page (
http://camino.cs.ucl.ac.uk/index.php?n=Man.Selectshells) there is a flag
named -unweightedb which specifies shells representing B=0 which are not
actually at that value (i.e. HCP data where b=5 is the b=0 condition).  I
tried the following command with the latest binary:

selectshells -inputfile tensor.nii -schemefile dwi.scheme -maxbval 1.5E09
-outputroot test -minbval 1.1E07 -unweightedb 1E07

In this case b< 10 (1E7) should be the max b=0 condition, and 11 (1.1E07)
<= b <= 1500 (1.5E9) should be the range of values included in the
subshell.  I keep getting an unable to parse -unweightedb error no matter
how I try it.  Is this option OBSOLETE?


If I use -minbval with the default value of 0 , what happens in the case
where my minimum is b=5?  Will it automatically detect that b=5 is the
lowest number and assume this is the unweighted option since -unweightedb
does not work?


2) Restore - In some of the Camino user posts the HCP b=5 would create
errors since a B=0 is not detected

a) Is this issue resolved or is the solution of manually changing scheme
files where b=5 to b=0 the way it works?
--If it is resolved, can the calculations handle b=5 or does the program
take the lowest b value and assume it is b=0 internally or is the scheme
file modified?  I am curious how this was handled.

b) Can Restore algorithm make more accurate calculations using all 3 shells
(1k2k3k) or is < 1500 still the preferred route?  My guess is that it is
NOT able to use all three shells, but I wanted to verify.

c) As for the noise estimate I took the sigma of the background [1-head
mask (large to avoid ghosting/inside head) ].  This works well for Siemens
data, however from my understanding Philips may do some sort of
masking/noise suppression outside of the brain.  Has this been an issue in
the past and if so have you tried another region to "estimate noise" inside
the brain (i.e gap between brain and skull etc) for Philips data in the
past?


Thanks,
Ajay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.nitrc.org/pipermail/camino-users/attachments/20170610/ab65398e/attachment.html>


More information about the Camino-users mailing list