Hello,

I have a twofold question:

1) When adding custom ROIs in the basic setup, should they be in structural or functional space ?
2) After running preprocessing and moving to the denoising step, my custom ROI, considered as an atlas file (one region devided into labeled subregions), is considered as one cluster instead of ROI1, ROI2, ROI3, ROI4... ROI10 (as per their original label). I did check the "Atlas file" box. My question is how can I make the conn toolbox read the subregions similar to how it reads the default "atlas" ROI ?

Thank you for your time.

Jimmy