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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  2004

FSL 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

FEAT first-level 2x2 factorial ANOVA

From:

Tommi Raij <[log in to unmask]>

Reply-To:

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

Date:

Mon, 16 Feb 2004 09:23:42 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (149 lines)

Hi all,

I am trying to build a fMRI FEAT analysis that would analyze 2x2 factorial
ANOVA interactions as a first-level analysis in a single subject. In the FSL
archives this was mainly discussed as a second-level analysis, but I hope
this can be done as a first-level analysis as well (the FEAT manual
suggested this possibility but did not describe it much further). A major
concern in this type of analysis is that the interaction is typically much
smaller than the main effects. Thus any confounding effects or mistakes in
the analysis can easily modify or become the whole outcome of a interaction
study. Any advice how to set this analysis up _really_ correctly in FEAT
would be much appreciated.

In the stimuli, there are 2 factors (A and B) at 2 levels (ON and OFF). Thus
there are 4 types of stimuli: A0B0 = REST, A1B0 = A, A0B1 = B, and A1B1 =
AB. Physically, the "AB" condition corresponds to a stimulus where both A
and B are presented simultaneously. Stimulus duration is 0.3 seconds for all
stimuli A/B/AB.

We use a sparse sampling design (clustered volume acquisition) with one full
volume EPI every 10 seconds (taking one full volume of 24 slices takes 1.2
seconds, which is followed by a pause of 8.8 seconds when no EPI data is
collected). Each EPI is preceded by a single stimulus (one of the four
categories REST/A/B/AB) at 4 seconds before EPI onset. The stimuli are
presented in a random order. We collect about 50 full EPI volumes for each
of the 4 stimulus categories (hence this is a repeated measures ANOVA with
50 values for each cell, for each voxel separately).

In all the considerations below, EV1=stimulus A, EV2=stimulus B, and
EV3=stimulus AB (_not_ the interaction). REST is defined implicitly by
exclusion (as time periods when none of the paradigm files suggest there
would have been a stimulus) and thus there is no separate paradigm file for
REST.

The FEAT manual (Appendix A) describes "how to model nonlinear interactions
between two EVs" (factors). I here assume that the "interaction" discussed
in the FEAT manual at Appendix A is the 2x2 factorial ANOVA interaction,
please correct me if I am wrong. Below I have three suggestions; Suggestion
1 is what the manual would seem to indicate but that does not work.




*** Suggestion 1. The manual suggests "setting up two original EVs"
(corresponding to stimuli A and B when presented alone?), and then "an
interaction term, which will will only be up when both the original EVs are
up, and down otherwise" (corresponding to stimulus AB?). However for
Interaction, it is not possible to assign a paradigm file, and paradigm
files can only be assigned to EV1 and EV2 (A and B). Since calculation of
interaction requires values from all 4 cells (REST, A, B, and AB), there
must be some way of telling FEAT how to distinguish between AB and REST
events. The logical conclusion would be to construct two paradigm files, one
that is "1" always when stimulus A is present (thus, for A and AB stimuli),
and another that is "1" always when the stimulus B is present (thus, for B
and AB stimuli) - thus the AB stimuli occur when both of the two paradigm
files show "1". Then one would simply generate a third EV (EV3) and select
that as Interaction between EV1 and EV2. Then one would build the following
4 contrasts:

OC1 [1 0 0] ; for main effect A
OC2 [0 1 0] ; for main effect B
OC3 [0 0 1] ; for Interaction (positive)
OC4 [0 0 -1] ; for Interaction (negative)

However this leads to that EV1 and EV2 are overlapping (for AB stimuli, both
are "1" at the same time), and thus they are NOT independent of each other.
This violates the basic requirement of the GLM that all events be
independent of each other. Attempts to set up the analysis this way result
in an error of the type "Problem with processing the model: At least one EV
is (close to) a linear combination of the others. You should probably alter
your design. (Design matrix is rand deficient - ratio of min:max eigenvalues
in SVD matrix is 1.283201e-06)".




*** Suggestion 2. Given the failure of Suggestion 1, the only way to tell
all the 4 cells apart (REST, A, B, and AB) would be to have at least 3
paradigm files (for A, B, and AB; REST would be implicit from the other
three files).

Then, then to analyze the interaction, one should have three paradigm files
(all in 3-column format).
Paradigm file 1 has "1" every time only the stimulus A is on,
Paradigm file 2 has "1" every time only the stimulus B is on, and
Paradigm file 3 has "1" every time the AB stimulus is on.
Now the three paradigm files are completely non-overlapping and thus
independent of each other, and GLM should be happy.

Then I should set the number of original EVs as 4, assign the Custom (3
column format) paradigm files for EV1 (A), EV2 (B), EV3 (AB), and set
"Interaction" for EV4, Between EVs [1 2 3] (all three buttons 1-3 selected
for choosing the interaction components).

In the contrasts I should select 5 contrasts (for original EVs?) with
OC1 [1 0 0 0] ;A vs. REST
OC2 [0 1 0 0] ;B vs. REST
OC3 [0 0 1 0] ;AB vs. REST
OC4 [0 0 0 1] ;Interaction (+)
OC5 [0 0 0 -1] ; Interaction (-)

No F-tests are selected in this approach.

With this approach, there is again an error of the type "Problem with
processing the model: At least one EV is (close to) a linear combination of
the others. You should probably alter your design. (Design matrix is rand
deficient - ratio of min:max eigenvalues in SVD matrix is 1.283201e-06)".
Also according to the FEAT manual [regarding
Stats/First-level/EVs/Interaction], "this EV [interaction] is produced by
multiplying together selected EVs". Is this different from a 2x2 factorial
ANOVA interaction?




*** Suggestion 3. This is exactly the same as Suggestion 2 (including the
above settings for EVs and contrasts), but now I add four F-tests in the
General Linear Model/Contrasts & F-tests:

           F F F F
           1 2 3 4
OC1 [X - - -]
OC2 [- X - -]
OC3 [- - X -]
OC4 [- - - X]
OC5 [- - - X]

The OC4 and OC5 F-tests should give the 2x2 factorial ANOVA interactions
(for positive and negative interactions, respectively).

*****************

Which one, if any, of the above would be the correct FEAT setting for
first-level 2x2 factorial ANOVA w/ repeated measures ?

Thanks in advance,

Tommi

--
Tommi Raij, M.D., Ph.D.
Research Fellow
MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging
Building 149, 13th Street, Mailcode 149-2301
Charlestown, MA 02129 U.S.A.

[log in to unmask]
FAX 1-617-726-7422

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