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  July 2009

FSL July 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Combining command-line and FEATs for 1st-level analysis

From:

Mark Jenkinson <[log in to unmask]>

Reply-To:

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

Date:

Tue, 7 Jul 2009 14:52:36 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (110 lines)

Hi,

I would recommend the following:
  - run the first level analysis with FEAT for all subjects and have
	everything turned on, including registration, but deselect the
	standard image and only select the Main structural image
	(this will generate the example_func to highres registrations)
  - re-run one case with just registration turned on (everything
	else off) and select both structural and standard images,
	including the non-linear registration (this will generate the
	desired highres2standard registrations) - probably best to
	call the output something quite different here to avoid
	confusion with the previous feat directories
  - copy all the highres2standard files from the session above to
	all of the .feat/reg directories of the sessions for that subject
  - in each session's feat directory run updatefeatreg
This will then generate full first-level analyses with all the  
registration
details done, but only having run the highres to standard registration
once.

Regarding the motion EVs, you can simply select this as normal in the  
first
step above.

For the fsl_motion_outliers, I'm afraid we are still in the process of
running experiments and preparing a paper so I can't really comment
on relative performance.  Anecdotally it seems to work well on some
datasets but not all.  It does use a different way of determining the
outliers (for example, if motion correction fails for a volume this will
be detected here but may not be obvious from the mcflirt rms file, and
it is also more sensitive to cases of strong within-volume motion  
effects).
To use it you just need to run this initially, create appropriately  
named
confound ev files and then specify them in the FEAT setup in the first
step of the above analysis.

Hope this helps.
All the best,
	Mark




On 4 Jul 2009, at 15:15, Jonathan Ipser wrote:

> Hello everyone,
>
> I was hoping for some reassurance that I am on the right track re  
> 1st level
> analyses.
>
> The data I have consists of a total of 24 runs per participant (12 per
> session). Rather than running the entire first-level analysis using  
> the FEAT
> GUI for each of these runs, which would have involved registering the
> structural to standard images 24 times per participant, I attempted  
> to save
> some time by conducting the structural to standard registration only  
> once
> per subject per session, using flirt via the command line. I have  
> still used
> FEAT for motion correction, but made sure I deselected all the  
> options on
> the registration tab.
>
> I would now like to use FEAT for the remainder of the 1st level  
> analysis. I
> am assuming that the 4D image I should use as input for the stats  
> step is
> the filtered_func_data.nii image in the main output directory. Is  
> this correct?
>
> I would also like to add motion parameters as events of no interest  
> using
> FEAT. However, the "add motion parameters to the model" button is  
> disabled
> unless you conduct the prestats and stats in the same FEAT run. From  
> reading
> this mailing list, it seems that one can add the 3 translation and 3
> rotation parameter estimates from the prefiltered_func_data_mcf.par  
> file
> using the "add additional confound EVs" button. Using the 1-column  
> format,
> it should be possible to select this file directly, as the format of  
> the
> prefiltered_func_data_mcf.par is consistent with the format of  
> multiple
> 1-column EVs in the same file (TRs = rows, and EVs = columns). Is  
> this the case?
>
> Finally, although I intended including columns modeling individual  
> spikes in
> the timeseries (identified from the  
> prefiltered_func_data_mcf_rel.rms file)
> as additional EVs in this confound EV file, it seems that a better  
> option
> might be to use the fsl_motion_outliers script to generate these EVs  
> (which
> then can presumably be added to the confound EV file). Is there any
> literature on the fsl_motion_outliers algorithm, perhaps comparing the
> performance of these two methods?
>
> Best,
> Jonathan Ipser
> Department of Psychiatry and Mental Health
> University of Cape Town
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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