I don’t know that there is a good FIX training file for data like that.  It is quite high for resolution (higher than we went at 7T for HCP) and quite slow for TR.  As for slice timing correction, the HCP has avoided the issue by making sure to get sub-1 second TR data because of its benefits for data denoising and statistical power.  Slice timing correction is problematic in the setting of subject motion (either subject has moved and slice timing correction interpolates across different positions if done before or if done after slice timing correction interpolates across different slice times).  I don’t know if anyone has a principled solution to this dilemma.  

Matt.

From: FSL - FMRIB's Software Library <[log in to unmask]> on behalf of "Wu, Junjie" <[log in to unmask]>
Reply-To: FSL - FMRIB's Software Library <[log in to unmask]>
Date: Thursday, February 14, 2019 at 8:50 PM
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: [FSL] Slice timing correction and FIX

The rs-fMRI data were acquired on a 3T scanner with Multiband factor=3, TR=1.89s, Resolution=1.5x1.5x1.5mm, Session=10mins.

Best,
Junjie


On Thu, Feb 14, 2019 at 5:51 PM Glasser, Matthew <[log in to unmask]> wrote:
It is surprising that you have a TR=2s with multi-band data.  What kind of data is this?v  That will be important to answer all these questions.  

Matt.

From: FSL - FMRIB's Software Library <[log in to unmask]> on behalf of "Wu, Junjie" <[log in to unmask]>
Reply-To: FSL - FMRIB's Software Library <[log in to unmask]>
Date: Thursday, February 14, 2019 at 3:56 PM
To: "[log in to unmask]" <[log in to unmask]>
Subject: [FSL] Slice timing correction and FIX

Dear FSL community,

I am using MELODIC to process multiband resting state fMRI data. I have questions on slice timing correction and FIX.

1) Should slice timing correction be used for resting state data of TR = ~ 2s? Slice timing correction is not included in Human Connectome Project pipeline. However, HCP data would not be affected much by slice timing effects because TR of the HCP data is relatively short (720ms) as compared to TR of conventional fMRI data (about 1.5s - 3s).

2) If slice timing correction is not strongly unrecommended, how to perform slice timing correction for multiband data?

3) Is it appropriate to use trained-weights files supplied with FIX to remove noise components in an fMRI dataset, where the acquisition and preprocessing parameters are close to one of the example training-input data? In this case, how well dose FIX perform?

Thanks,
Junjie


To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1

 


The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.



To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1



To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1

 


The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.



To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1