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

Help for SPM Archives


SPM Archives

SPM Archives


SPM@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

SPM Home

SPM Home

SPM  2000

SPM 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: group analysis

From:

Karl Friston <[log in to unmask]>

Reply-To:

Karl Friston <[log in to unmask]>

Date:

Mon, 17 Apr 2000 19:37:11 +0100 (BST)

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (157 lines)

Dear Anja,

> I have a question concerning group analysis in spm99. In the first step
> of statistics, when I want to create the design matrix it is very hard
> to type all this data in. Is it possible to create the Design matrix in
> an matlab window by myself?  I loaded the mat-file of an existing
> Design matrix, but I don't understand the numbers in the array xX.X. I
> understood that the number of rows is the number of pictures of my
> data, and that the columns are the different conditions and sessions.
> Somehow the numbers seem to code for the onset times of stimulation
> (negative ones for no stimulation and positive ones for stimulation?),
> but what exactly do the floats code for?


It would be difficult to v create a fMRI design matrix by hand (the
routine spm_fMRI_design was built to do this).  You could look at the
batch code written by J-B and his colleagues to help you if you wanted
to pursue a 'by-hand' approach.

The following is the help for spm_fMRI_design which contains the
necessary information on structures.

I hope this helps - Karl



>> help spm_fMRI_design

  Assembles a design matrix for fMRI studies
  FORMAT [xX,Sess] = spm_fMRI_design(nscan,RT)
 
  nscan   - n vector {nscan(n) = number of scans in session n}
  RT      - intercans interval {seconds}
 
  xX            - structure describing design matrix
  xX.X          - design matrix
  xX.dt         - time bin {secs}
  xX.RT         - Repetition time {secs}
  xX.iH         - vector of H partition (condition effects)      indices,
  xX.iC         - vector of C partition (covariates of interest) indices
  xX.iB         - vector of B partition (block effects)          indices
  xX.iG         - vector of G partition (nuisance variables)     indices
  xX.Xnames     - cellstr of effect names corresponding to columns
                  of the design matrix
 
  Sess{s}.BFstr    - basis function description string
  Sess{s}.DSstr    - Design description string
  Sess{s}.rep      - session replication flag
  Sess{s}.row      - scan   indices      for session s
  Sess{s}.col      - effect indices      for session s
  Sess{s}.name{i}  - of ith trial type   for session s
  Sess{s}.ind{i}   - column indices      for ith trial type {within session}
  Sess{s}.bf{i}    - basis functions     for ith trial type
  Sess{s}.sf{i}    - stick functions     for ith trial type
  Sess{s}.ons{i}   - stimuli onset times for ith trial type (secs)
  Sess{s}.pst{i}   - peristimulus times  for ith trial type (secs)
  Sess{s}.Pv{i}    - vector of paramters for ith trial type
  Sess{s}.Pname{i} - name   of paramters for ith trial type
 
  saves SPM_fMRIDesMtx.mat (xX Sess)
 _______________________________________________________________________
 
  spm_fMRI_design allows you to build design matrices with separable
  session-specific partitions.  Each partition may be the same (in which
  case it is only necessary to specify it once) or different.  Responses
  can be either event- or epoch related, where the latter model prolonged
  and possibly time-varying responses to state-related changes in
  experimental conditions.  Event-related response are modelled in terms
  of responses to instantaneous events.  Mathematically they are both
  modelled by convolving a series of delta (or stick) functions,
  indicating the onset of an event or epoch with a set of basis
  functions.  These basis functions can be very simple, like a box car,
  or may model voxel-specific forms of evoked responses with a linear
  combination of several basis functions (e.g.  a Fourier set).  Basis
  functions can be used to plot estimated responses to single events or
  epochs once the parameters (i.e.  basis function coefficients) have
  been estimated.  The importance of basis functions is that they provide
  a graceful transition between simple fixed response models (like the
  box-car) and finite impulse response (FIR) models, where there is one
  basis function for each scan following an event or epoch onset.  The
  nice thing about basis functions, compared to FIR models, is that data
  sampling and stimulus presentation does not have to be sychronized
  thereby allowing a uniform and unbiased sampling of peri-stimulus time.
 
  spm_fMRI_design allows you to combine both event- and epoch-related
  responses in the same model.  You are asked to specify the number
  of condition (epoch) or trial (event) types.  Epoch and event-related 
  responses are modeled in exactly the same way by first specifying their
  onsets [in terms of stimulus onset asynchronies (SOAs) or explicit onset 
  times] and then convolving with appropriate basis functions (short ones
  for event-related models and longer ones for epoch-related respones).
  Enter 0 to skip these if you only want to use regressors you have designed 
  outside spm_fMRI_design).
  
  Interactions or response modulations can enter at two levels.  Firstly
  the stick function itself can be modulated by some parametric variate
  (this can be time or some trial-specific variate like reaction time)
  modeling the interaction between the trial and the variate or, secondly
  interactions among the trials themselves can be modeled using a Volterra
  series formulation that accommodates interactions over time (and therefore
  within and between trial types).  The first sort of interaction is
  specified by extra (modulated) stick functions in Sess{s}.sf{i}.  If
  a polynomial expansion of the specified variate is requested there will
  be more than one additional column.  The corresponding name of the
  explanatory variables in X.Xname is Sn(s) trial i(p)[q] for the qth
  order expansion of the variate convolved with the pth basis function
  of the ith trial in the sth session.  If no parametric variate is
  specified the name is simply Sn(s) trial i(p).  Interactions among
  and within trials enter as new trial types but do not have .pst or .ons
  fields.  These interactions can be characterized later, in results, in
  terms of the corresponding second order Volterra Kernels.
 
  The design matrix is assembled on a much finer time scale (X.dt) than the 
  TR and is then subsampled at the acquisition times.
 
  Sess{s}.ons{i} contains stimulus onset times in seconds relative to the
  timing of the first scan and are provided to contruct stimuli when using 
  stochastic designs
 
 
  Notes on spm_get_ons, spm_get_bf and spm_Volterra are included below
  for convenience.
 
                            ----------------
 
  spm_get_ons contructs a cell of sparse delta functions specifying the
  onset of events or epochs (or both). These are convolved with a basis set
  at a later stage to give regressors that enter into the design matrix.
  Interactions of evoked responses with some parameter (time or a specified 
  variate Pv) enter at this stage as additional columns in sf with each delta
  function multiplied by the [expansion of the] trial-specific parameter.
  If parametric modulation is modeled, P contains the original variate and
  Pname is its name.  Otherwise P{i} = [] and Pname{i} = '';
 
                            ----------------
 
  spm_get_bf prompts for basis functions to model event or epoch-related
  responses.  The basis functions returned are unitary and orthonormal
  when defined as a function of peri-stimulus time in time-bins.
  It is at this point that the distinction between event and epoch-related 
  responses enters.
 
                            ----------------
 
  For first order expansions spm_Volterra simply convolves the causes
  (e.g. stick functions) in SF by the basis functions in BF to create
  a design matrix X.  For second order expansions new entries appear
  in IND, BF and name that correspond to the interaction among the
  orginal causes (if the events are sufficiently close in time).
  The basis functions for these are two dimensional and are used to
  assemble the second order kernel in spm_graph.m.  Second order effects
  are computed for only the first column of SF.
 


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

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
2000
1999
1998


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