Open Figsandcitrus opened 3 years ago
@a3sha2 could you please comment in this?
I am sorry @Figsandcitrus, for late response. Yes you are right, you have to change fds, fds:0.083 is based on 3 seconds TR to obtained fd threshold of 0.25 mm. With TR of 2s, it will be fds:0.125 (that is 2*.125= 0.25mm).
let me know it is clear or not
Describe the bug We use a modified fc-36p_spkreg.dsn with fmriprep20.2 results as input. The only varation from original dsn is that I set confound2_censor[2]=0 to avoid scrubbing (see pasted portion below). My question is: Do I have to change the "confound2_framewise [2]" value based on the TR? I am not sure if I can tell if the spike regressor considers the TR for detecting spikes, otherwise the spike regression criteria would be more stringent for TR=2s (.082=.16mm) than TR=3s (.083=.24).
I read #214 but I am not sure if it is suggesting to change fds, dv, or both for TR other than 3. and if fc-36p_spkreg.dsn scheme is much affected by this compared to despiking.
Design File
Error message None
Runtime Information Singluarity
Additional context Is qcfc utility supposed to help with these problems?