Quantcast
Channel: NITRC CONN : functional connectivity toolbox Forum: help
Viewing all articles
Browse latest Browse all 6861

functional_label

$
0
0
Hi all,

I am writing a script for my resting-state data preprocessing based on the NYU script. So far everything works well on my first trial using the default pipeline but I am now dropping the STC as we have a short TR=1.5s (multiband 3). I know that this TR is probably borderline candidate for correction (with 15-20% signal drop in worst cases when uncorrected) but I was advised that the signal I gain through STC will probably be negligible once the functional data is smoothed. So I proceed by spelling out my preproc step in the setup.preprocessing.steps line.

The problem is that I am confused by the functional_label step. Do I understand correctly that the step serves to label the functional data "original data", "mni-space data" and "smoothed data" in the default pipeline? How do I assign the value if that's the case, the default value [datestr(now)] does not look like the labels above. Also, part of the confusion is that I don't understand what "secondary data" means in the glossary.

Can anyone explain? I know that the batch will run without functional_label specified, the previous CONN default pipeline didn't seem to have it when I checked past manuals. Still, I don't want to miss out on what might be a super useful step just because I don't understand it. 

Thanks in advance,
Steve

Viewing all articles
Browse latest Browse all 6861

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>