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  October 2016

FSL October 2016

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: FAST, Sienax

From:

Lance Stevens <[log in to unmask]>

Reply-To:

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

Date:

Sun, 30 Oct 2016 16:46:26 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (75 lines)

Thank you Mark.

if I wanted to add SIENAX-derived head size as a covariate for FIRST
corrected output (not vertex results) and use, say, a standard
regression multiple regression model in a statistical package, would I
use subjects normalized BRAIN (surrogate for head size; for example,
calculated below from the practical [1192234.82]) to adjust or control
for head size? That is, BRAIN values could be a covariate/regressor,
along with other covariates, such as Medication and gender, all of
which may contribute some variation to the outcome variable FIRST
subcortical volume.

----------  convert brain volume into normalised volume  --------------

tissue             volume    unnormalised-volume
pgrey              496752.82 454866.29 (peripheral grey)
vcsf               79257.48 72574.44 (ventricular CSF)
GREY               584635.30 535338.46
WHITE              607599.52 556366.32
BRAIN              1192234.82 1091704.78

Best,
Lance

On Tue, Oct 25, 2016 at 4:46 PM, Mark Jenkinson
<[log in to unmask]> wrote:
> Hi,
>
> We don't really have a method that calculates TIV.  So comparing anything from FSL with TIV from some other package would not be very informative.  However, if you wanted to compare how various different measures performed as regressors in statistical correction or normalisation factors, then we would recommend using the VSCALING value from SIENAX.
>
> All the best,
>         Mark
>
>
>> On 23 Oct 2016, at 23:52, Lance Stevens <[log in to unmask]> wrote:
>>
>> Thank you Mark, especially for the detailed responses. I can see it
>> would be inappropriate to reintroduce TIV as a nuisance regressor in
>> the VBM or First vertex analyses.
>>
>> Initially, if I simply wanted to compare TIV as calculated in FSL, vs
>> TIV as calculated in Free Surfer (mri_segstats --subject subjid
>> --etiv-only), would SIENAX still be more appropriate than FAST?
>>
>> Thank you again.
>>
>> Lance
>>
>> On Sun, Oct 23, 2016 at 4:11 PM, Mark Jenkinson
>> <[log in to unmask]> wrote:
>>> Hi,
>>>
>>> See answers below.
>>>
>>>> I have 3 questions related to FAST and SIENAX
>>>>
>>>> Re FAST: While this link http://fsl.fmrib.ox.ac.uk/fsl/fslwiki/FAST/FAQ indicates that extracting a good estimate of CSF should involve use of a T2 (rather than T1) to obtain maximum contrast between skull and CSF, I assume an accurate sum of total intracranial volume (TIV) be calculated from a T1 by simply summing the 3 partial volume estimates of all three tissue type, CSF, GM and WM? That a T1 is sufficient is indicated by the FAST practical. I would expect that the TIV would include the meninges. Are both of these assumptions correct?
>>>
>>> TIV strictly should include everything inside the skull but not the bone.  However, you can't really distinguish bone from other dark air/tissue areas in a T1 clearly and so a T1 is poor for getting a precise TIV calculation.  The brain extraction that is done on T1 will exclude some of the CSF and other tissues inside the skull, and so it does not give a precise TIV.  T2 is better as the CSF is bright and so at least this can be clearly distinguished from bone. But the good news is that you normally don't need to have a precise TIV measurement to do things like correcting for head size, and so a reasonable surrogate, as you would get from a T1 is normally sufficient for this.
>>>
>>>> Re Sienax: Sienax is indicated for total brain tissue volume estimation in pathology, such as Alheimers. Is this referring to TIV or just the GM and WM (in some contexts CSF and also referred to as a tissue). The practical ( https://fsl.fmrib.ox.ac.uk/fslcourse/lectures/practicals/seg_struc/index.html#sienax ) suggests that Sienax takes TIV (CSF, GM, WM) but extracts just the GM/WM total combined volume. Is this correct?
>>>
>>> The main result from SIENAX is a brain tissue volume - which is just GM + WM.  It uses registration based on a skull estimate to correct for head size, but does not calculate TIV explicitly.  However, this surrogate for head size is sufficient to correct for the majority of the effects related to head size.
>>>
>>>> I have two groups: 10 patients with intermediate stage Parkinson’s Disease (PD) and 10 controls. I want to treat TIV as a nuisance covariate and remove is contribution to VBM cortical and FIRST subcortical estimates.  I would assume FAST could be applied to both PD and controls to arrive at TIV estimates that could be run in an ANCOVA model to eliminate contribution to the VBM and FIRST outcomes?
>>>
>>> We would recommend using the VSCALING output from SIENAX as the better surrogate for head size, rather than trying to use FAST to calculate TIV.  You can then use the VSCALING values in place of TIV values to perform an equivalent correction.  However, also note that VBM gives you values that are related to volumes in standard space and hence are already largely corrected for head size.  It is fine to put in a regressor in your analysis to remove anything left over (as correcting twice in this way will not be a problem) but do not divide the values by your VSCALING value (or TIV or any other surrogate) as that would reintroduce a head size dependence, which you do not want. So stick to linear corrections within the GLM (or equivalent regression models).  For FIRST the volumes are in native space, and so you can divide these or correct via regression, but the vertex analysis results can either be in native space or in standard space, depending on the options you've used.  If they are in standard (MNI) space then they are already corrected and it is like VBM - correcting again via regression is fine but normalising again by division would reintroduce a dependence and so should be avoided.
>>>
>>> All the best,
>>>        Mark
>>>
>>>
>>>
>

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