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  April 2010

FSL April 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

subject artifact in TBSS

From:

Mark Shen <[log in to unmask]>

Reply-To:

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

Date:

Fri, 16 Apr 2010 16:41:09 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (27 lines)

Hi FSL team,

After running 'tbss_2_reg -n' and 'tbss_3_postreg -S' on a large sample of toddlers, the resulting mean_FA_skeleton and every volume of all_FA had a large dropout in right superior frontal lobe.  I traced this artifact back to a single FA map that had this same dropout.

Here are my specific questions, and I have also detailed my processing pipeline.  I thank you very much in advance!
1) Is it possible that 1 faulty subject with artifact could apply this artifact to all other subjects during tbss_2_reg and tbss_3_postreg?
2) Is it possible to remove a subject (and all associated files) from a TBSS analysis after tbss_2_reg has already ran?
3) Could the troubleshooting attempt in #2 affect the statistical analysis and power to detect direct between-group differences?

Here are the the steps of my processing pipeline.  My questions (from above) pertain to the steps marked with ***:
-I am running all TBSS steps on FSL version 4.1.4., using a quadcore MacPro running OX 10.5.8
-The sample is a between-group design of toddlers N=77, clinical vs. controls. 
-I originally ran tbss_2_reg -n (flag), and it completed after 17 days without crashing.
-I ran tbss_3_postreg -S (flag), and then I checked the alignment of all_FA under mean_FA_skeleton.
-I discovered that every volume (0-76) of all_FA had a large signal dropout in the right superior frontal lobe.  The mean_FA_skeleton also had this artifact.
-After some investigation, I found that the FA map for 1 single clinical subject had this artifact.  I assumed that this one subject was causing all the volumes of all_FA and the mean_FA_skeleton to have this artifact.***
-Rather than removing the 1 subject from the start and re-running tbss_2_reg for another 17 days, I tried the following: I removed all files written during tbss_3_postreg and then removed all files that were written during tbss_2_reg that contained the file name of the faulty subject (i.e. all the nonlinear warps created from the faulty subject during tbss_2_reg).***
-I then ran tbss_3_postreg again, and now every volume of the new all_FA (0-75) did not have the artifact, and neither did mean_FA_skeleton.
-Thus, I proceeded with tbss_4_prestats 0.2 (threshold) and ran randomise with the --T2 (TFCE flag).
-The corrected (corrp) statmap did not show any significant group differences, even at very low (1-p=.60) threshold.***

Thank you so much for your help.

Mark Shen
M.I.N.D. Institute
University of California, Davis

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