You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In setting up post processing options in clpipe_config.json, I am a little confused about the GlobalSignalRegression field. This field does not automatically appear in the "PostProcessingOptions" when a config file is generated. However, I can see that you have implemented it in "ProcessingStreams".
I can see that "global_signal" is default included in the "Confounds", "ConfoundsQuad", "ConfoundsDerive", and "ConfoundsQuadDerive" fields. I am assuming this is the equivalent of "GlobalSignalRegression: True/False. Include global signal into nuisance regression. Defaults to True." as noted in the documentation, but I find it confusing that this field doesnt appear as noted in the documentation. I am hoping you could clarify that in the documentation/config file.
Thanks! Mackenzie
The text was updated successfully, but these errors were encountered:
Hi Teague,
In setting up post processing options in clpipe_config.json, I am a little confused about the GlobalSignalRegression field. This field does not automatically appear in the "PostProcessingOptions" when a config file is generated. However, I can see that you have implemented it in "ProcessingStreams".
I can see that "global_signal" is default included in the "Confounds", "ConfoundsQuad", "ConfoundsDerive", and "ConfoundsQuadDerive" fields. I am assuming this is the equivalent of "GlobalSignalRegression: True/False. Include global signal into nuisance regression. Defaults to True." as noted in the documentation, but I find it confusing that this field doesnt appear as noted in the documentation. I am hoping you could clarify that in the documentation/config file.
Thanks! Mackenzie
The text was updated successfully, but these errors were encountered: