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

FSL March 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Discrepancies between feat output and fslview

From:

Steve Smith <[log in to unmask]>

Reply-To:

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

Date:

Thu, 5 Mar 2009 05:30:20 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (201 lines)

Hi, the reason that just thresholding voxelwise the zstat image  
doesn't look like thresh_zstat is probably because you chose a  
different method than voxelwise thresholding in FEAT  ;-)

If you chose cluster-based thresholding then only clusters large  
enough to be significant will have been included in thresh_zstat - so  
that's not the same as just thresholding voxelwise in FSLView.

Cheers.


On 5 Mar 2009, at 00:57, Lin Nga wrote:

> Liam
>
> Typing 2.3 into the min box works just fine. My question is just,  
> why is it
> that for the same given range, my zstat does not look like my  
> thresh_zstat
> image? From my understanding, thresh_zstat is the thresholded z  
> statistics
> image and zstat is the raw z statistics image; is this wrong? If I  
> play
> around with the threshold with the zstat image, does this not tell me
> anything significant?
>
> Thanks again,
> Lin
>
> On Wed, 4 Mar 2009 16:40:34 -0800, Nestor, Liam (Contractor)
> <[log in to unmask]> wrote:
>
>> Lin
>>
>> Overlay the thresh_zstat. When you do this, your underlay image  
>> should be
> entirely covered by (but you should able to see signs of clusters
> underneath). Now type 2.3 into the min box. Does typing 2.3 (your z  
> stat
> threshold as used in FEAT) still leave the brain very covered in  
> activity?
> If so, playing around with the min value (e.g., try typing 2.81  
> which is
> p=0.005) might give you a better idea of thresholding for an
> additiona/futurel FEAT analysis.
>>
>> Your axial (horizontal) image map in fslview should look like that  
>> in the
> report. I have just checked some of my files to confirm this.
>>
>> Liam.
>>
>>
>>
>>
>> *******************************************
>> Liam Nestor, Ph.D
>> Office C8-523
>> Laboratory for Molecular Neuroimaging
>> Semel Institute for Neuroscience and Human Behavior
>> 760 Westwood Plaza
>> Los Angeles 90024
>> Tel: 310-206-0655
>> E-mail: [log in to unmask]
>> *******************************************
>> ________________________________________
>> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf  
>> Of Lin
> Nga [[log in to unmask]]
>> Sent: Wednesday, March 04, 2009 4:13 PM
>> To: [log in to unmask]
>> Subject: Re: [FSL] Discrepancies between feat output and fslview
>>
>> Hi Liam,
>>
>> Thank you for your response. Typing 2.3 into the min box does  
>> indeed make
>> the image look like the feat output but that wasn't really my main
>> confusion. What I'd like to know is that if I overlay the raw zstat  
>> file and
>> change the min and max threshold to reflect those given in the feat  
>> report (
>> 2.3 and 3.4 respectively ), this does not look anything like the feat
>> report. If I want to play around with the threshold to see if this  
>> affects
>> my results, should I not be doing so with the zstatX.nii.gz and use
>> thresh_zstatX.nii.gz instead? But isn't the thresh_zstatX.nii.gz  
>> image a
>> result of thresholding at 2.3?
>>
>> Thanks,
>> Lin
>>
>> On Wed, 4 Mar 2009 14:49:12 -0800, Nestor, Liam (Contractor)
>> <[log in to unmask]> wrote:
>>
>>> Lin
>>>
>>> I think what is happening here is you are thresholding at 2.3 in  
>>> your FEAT
>> analyses; the end product of which is a FEAT report telling you  
>> that the
>> range is from 2.3 (min) to 3.4 (max).
>>>
>>> When you overlay your thresholded zstat file on top of your  
>>> 152MNI, you
>> need to type 2.3 into the min box provided.
>>>
>>> Try doing this and see what happens.
>>>
>>> Liam.
>>>
>>> *******************************************
>>> Liam Nestor, Ph.D
>>> Office C8-523
>>> Laboratory for Molecular Neuroimaging
>>> Semel Institute for Neuroscience and Human Behavior
>>> 760 Westwood Plaza
>>> Los Angeles 90024
>>> Tel: 310-206-0655
>>> E-mail: [log in to unmask]
>>> *******************************************
>>> ________________________________________
>>> From: FSL - FMRIB's Software Library [[log in to unmask]] On  
>>> Behalf Of Lin
>> Nga [[log in to unmask]]
>>> Sent: Wednesday, March 04, 2009 2:47 PM
>>> To: [log in to unmask]
>>> Subject: Re: [FSL] Discrepancies between feat output and fslview
>>>
>>> I also want to add a couple more thing I noted. I opened up the  
>>> thresh_zstat
>>> in fslview, which should look like what is displayed on the feat  
>>> report (and
>>> it does as expected), and the threshold ranges from 0 to 2.9. Why  
>>> does the
>>> range on the feat report say 2.3 to 3.4 when the thresholded image  
>>> goes from
>>> 0 to 2.9? Could someone please explain what is going on here?
>>>
>>> Thanks for the help,
>>> Lin
>>>
>>> On Wed, 4 Mar 2009 21:38:13 +0000, Lin Nga <[log in to unmask]> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> I am looking at one zstat image for one cope of a group analysis.  
>>>> I have the
>>>> zstat overlay the bg_image in fslview and I adjusted the  
>>>> threshold to match
>>>> that of the feat output (in my case 2.3 to 3.4). What I see in  
>>>> fslview does
>>>> not look like what I see in the feat output. What is wrong here?  
>>>> Shouldn'
>>>> the two look the same? Am I looking at the wrong statistical image?
>>>>
>>>> Thank you so much,
>>>> Lin
>>>
>>> IMPORTANT WARNING:  This email (and any attachments) is only  
>>> intended for
>> the use of the person or entity to which it is addressed, and may  
>> contain
>> information that is privileged and confidential.  You, the  
>> recipient, are
>> obligated to maintain it in a safe, secure and confidential manner.
>> Unauthorized redisclosure or failure to maintain confidentiality  
>> may subject
>> you to federal and state penalties. If you are not the intended  
>> recipient,
>> please immediately notify us by return email, and delete this  
>> message from
>> your computer.
>>
>> IMPORTANT WARNING:  This email (and any attachments) is only  
>> intended for
> the use of the person or entity to which it is addressed, and may  
> contain
> information that is privileged and confidential.  You, the  
> recipient, are
> obligated to maintain it in a safe, secure and confidential manner.
> Unauthorized redisclosure or failure to maintain confidentiality may  
> subject
> you to federal and state penalties. If you are not the intended  
> recipient,
> please immediately notify us by return email, and delete this  
> message from
> your computer.
>


---------------------------------------------------------------------------
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director,  Oxford University FMRIB Centre

FMRIB, JR Hospital, Headington, Oxford  OX3 9DU, UK
+44 (0) 1865 222726  (fax 222717)
[log in to unmask]    http://www.fmrib.ox.ac.uk/~steve
---------------------------------------------------------------------------

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