Back to PLS Help

resting state with PLS
sinabagheri7@yahoo.com
Posted on 01/31/16 15:03:19
Number of posts: 1

Dear PLS experts,

I am new with PLS and sorry if my question seems trivial.

I am planning to compare spatial patterns (similarity and differences) of resting state functional connectivity of two seeds over 2 years (two time points).  I have a question about how to optimally set this up.

Let’s assume that we have one time point for now.

I am planning to run a fake task PLS first to extract the signal for two ROIs. When I set up task PLS module, I only define ONE condition with TRs for the onset of each block and then put 5TR as block length. That means if I have 170 volumes (TR = 2), the onset and during should look like below:

Condition1:

Onset: 0 5.5TR 11TR 16.5TR 22TR 27.5TR 33TR 38.5TR 44TR 49.5TR 55TR 60.5TR 66TR 71.5TR 77 TR

Length: 5TR (10sec)

But PLS average across all blocks within a condition, so instead of a figure 1B (demonstrating correlation scores for 30 blocks) presented in Grig and Grady, I get one averaged block for my only condition. So, I am just wondering if one has to define blocks as different conditions during creating of session files? Or instead one should split Resting state fMRI data into a number of blocks (using for example fslsplit) and set them as different runs, and then create data mat with “not-averaging-across-run” option?

Thanks for your help.

Sina

Replies:

Untitled Post
rmcintosh
Posted on 01/31/16 15:36:25
Number of posts: 394
rmcintosh replies:

quote:

Dear PLS experts,

I am new with PLS and sorry if my question seems trivial.

I am planning to compare spatial patterns (similarity and differences) of resting state functional connectivity of two seeds over 2 years (two time points).  I have a question about how to optimally set this up.

Let’s assume that we have one time point for now.

I am planning to run a fake task PLS first to extract the signal for two ROIs. When I set up task PLS module, I only define ONE condition with TRs for the onset of each block and then put 5TR as block length. That means if I have 170 volumes (TR = 2), the onset and during should look like below:

Condition1:

Onset: 0 5.5TR 11TR 16.5TR 22TR 27.5TR 33TR 38.5TR 44TR 49.5TR 55TR 60.5TR 66TR 71.5TR 77 TR

Length: 5TR (10sec)

But PLS average across all blocks within a condition, so instead of a figure 1B (demonstrating correlation scores for 30 blocks) presented in Grig and Grady, I get one averaged block for my only condition. So, I am just wondering if one has to define blocks as different conditions during creating of session files? Or instead one should split Resting state fMRI data into a number of blocks (using for example fslsplit) and set them as different runs, and then create data mat with “not-averaging-across-run” option?

Thanks for your help.

Sina

thanks for your question. Sina.

For now you will have use your option #2, which is what Grigg & Grady did.  We are working on a new release of PLS that will allow more flexibility, but it will be several more months before it is available

 

Randy




Login to reply to this topic.

Contact Us:

3560 Bathurst Street
Toronto, Ontario
Canada M6A 2E1
Phone: (416) 785-2500

Baycrest is an academic health sciences centre fully affiliated with the University of Toronto