JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FSL Archives


FSL Archives

FSL Archives


FSL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  May 2012

FSL May 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Round 2: Change in functional connectivity between pre- and post-conditions using randomise

From:

Lorena Jimenez-Castro <[log in to unmask]>

Reply-To:

FSL - FMRIB's Software Library <[log in to unmask]>

Date:

Mon, 14 May 2012 16:59:05 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

Dear Tom and Bettyann thanks a lot for your valuable comments!   

I would like to confirm that I understand what you wrote and commented previously. So my understanding is that I would need to run a second level analysis ON EACH  subject SEPARATELY using a paired t-test, 

i.e,  ONE second level FEAT for subjects 1: 
input pre_subj_1 and post_subject 1; design paired-t-test; output:  COPE1 pre> post for subject_1, COPE 2: Post > pre for subject 1, and doing that for each subjects. In that design  I would like to model the mean positive correlation and negative correlation So, COPE 3 mean pre_condition, COPE 4: mean _post_condition 


Let's say I have four subjects, I would then have to run two randomize separately as follow: 

1) randomise  -i COPE1 pre> post for subject_1 COPE1 pre> post for subject_2 COPE1 pre> post for subject_3 COPE1 pre> post for subject_4 -o pre>post.nii -d single_group_average.mat -t single_group_average.con -T -m <mask>  

2) randomise  -i COPE2 Post > pre_for_subject_1  COPE2_Post > pre_for_subject_2   COPE2_Post > pre_for_subject_3 COPE2 Post >pre_for subject_4 -o Post >pre.nii -d single_group_average.mat -t single_group_average.con -T -m <mask> 


Then if I want to mask the positive correlation and negative correlation I would need to mask the output from randomize as follow:
pre>post.nii masked with COPE 3 mean pre_condition (mean form second level analysis) 

Post > pre masked with COPE 4: mean _post_condition ((mean form second level analysis) 

Questions: 
A) Am I on the right track?

B) Is it the same to input in the second level analysis in FEAT all of the fist level analysis together as explained at:
http://www.fmrib.ox.ac.uk/fslcourse/lectures/practicals/feat2/index.htm instead of doing the second level analysis for each subjects separately (as I described above)? 

C) Following the web page http://www.fmrib.ox.ac.uk/fslcourse/lectures/practicals/feat2/index.htm, and the example described above,  Is it possible to finish the analysis in the second level and to try to publish those results? If not, Why is it necessary to perform a third level analysis in this case?

I would really appreciate your comments and advice on this matter

Thank you very much

Lorena Jiménez Castro, MD




________________________________________
Re: [FSL] Round 2: Change in functional connectivity between pre- and post-conditions using randomise

FROM: bettyann
 
TO: [log in to unmask]
 
Correction on my previous post ...

Since my experiment consists of two conditions -- Pre and Post -- and I want to model the _difference_ between these conditions, I need to follow the 'Paired t test' example shown at:
http://www.fmrib.ox.ac.uk/fslcourse/lectures/practicals/feat2/index.htm

This practical states after the bullet description of 'Level 2':

Note that as well as the COPEs, FEAT passes the variance of these COPEs ("varcopes"), and even the uncertainty in the variance of these COPEs ("tdofs" - degrees-of-freedom), between the different levels.

This is what I want.  Once I complete this paired t-test 2nd level analysis, I can then do the 3rd level, between-subject analysis described under "We are now ready to setup the third level, between-subject, analysis."



> Not surprising, the FSL group has provided a discussion and example of how to implement this 2nd level fixed effects analysis.  I'll follow this:
> 
> http://www.fmrib.ox.ac.uk/fslcourse/lectures/practicals/feat2/index.htm
> see:
> Group difference with multiple sessions for each subject
> 
> 
> 
>> Ah, yes!  This is good.  I do want to use the information provided by the varcopes.
>> 
>> Would I feed the resulting cope1 volumes into randomise?  Or would I use the zstat1 volumes as input to randomise?  
>> 
>> This gets back to my original question about using beta weights (cope1) as a measure of functional connectivity (no noise weighting factor) vs. using z-scores (zstat1) as a measure (includes noise weighting; is a transformed expression of correlation).
>> 
>> Thanks,
>> * ba
>> 
>> 
>> 
>>> In actual fact, the best thing to do would be to perform a fixed
>>> effects 2nd level analysis on each subject's connectivity data to
>>> calculate the difference between sessions for each subject. The cope
>>> images from such an analysis would represent the change in
>>> connectivity from session 1 to session 2, and could then be entered
>>> into a randomise group analysis. This would have the advantage of
>>> using the varcopes from the 1st level connectivity analysis.
>>> 
>>> -Tom

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager