help
help > Why are task conditions recommended to be used as confounds in denoising step?
Jun 21, 2022 02:06 PM | Jette de Vos
Why are task conditions recommended to be used as confounds in denoising step?
Dear,
We want to perform a gPPI analysi. As a default option the task conditions are entered as confounds in the denoising step, but these are the effects we are interested in, so we were wondering why it is recommended to regress them out as confounds?
If it does indeed make more sense to not include the task conditions as confounds, how do I prevent them from being used as confounds? I ran a batch script with no confounds specified, however, when loading the batch results in the GUI, the task conditions are still listed as confounds.
Best regards,
Jette
We want to perform a gPPI analysi. As a default option the task conditions are entered as confounds in the denoising step, but these are the effects we are interested in, so we were wondering why it is recommended to regress them out as confounds?
If it does indeed make more sense to not include the task conditions as confounds, how do I prevent them from being used as confounds? I ran a batch script with no confounds specified, however, when loading the batch results in the GUI, the task conditions are still listed as confounds.
Best regards,
Jette
Threaded View
Title | Author | Date |
---|---|---|
Jette de Vos | Jun 21, 2022 | |
Alfonso Nieto-Castanon | Jun 22, 2022 | |