Thanks for the quick responses. Figure 2 of that paper also answers my
other question.
Best,
Ariel
On Mon, Aug 5, 2013 at 1:56 PM, Xu, Junqian wrote:
> Ariel,
>
> We recommend people to use these calculated b-values (including
> cross-terms) instead of the input b-values. This was explained e
Ariel,
We recommend people to use these calculated b-values (including cross-terms)
instead of the input b-values. This was explained explicitly at page 137, 2nd
paragraph in
http://www.ncbi.nlm.nih.gov/pubmed/23702418
"Small b value variations due to the cross-terms between diffusion and imag
Yes you should take the bvalues in the bvals files literately. The actual average bvalue applied varies because of interactions between the imaging and diffusion gradients (cross-terms).
If you use FSL, you can deal with the bvalue/bvector gradient deviations with existing code. If not, ne
Hello everyone,
First of all, thanks for all the hard work on putting this data-set
together. I have been looking at some of the diffusion data and it's been a
good experience so far.
I have a question concerning the encoding of b values in this data set.
Nominally, data was collected in 3 differ
For the resting state data this was addressed previously:
http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0015710
Additional discussions of the benefits of multi-band imaging appear in:
http://www.sciencedirect.com/science/article/pii/S1053811913005065
http://www.science
Dear HCP-users,
I have a question about the resting state and task-evoked fMRI data collected
through the HCP. Why did you choose to only collect multiband EPI data? As far
as I know, no validation studies have been performed to verify that these new
multiband sequences yield similar results com
Hi Paula,
Thanks for raising these important questions about when various types of
"advanced" HCP datasets will be released. We apologize for the delayed
response, but internal discussions were needed in order to clarify the HCP's
general game plan on this front.
The current Q2 HCP data re