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 2007

FSL April 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: single voxel percentage signal change via featquery tool

From:

Paymon Hosseini <[log in to unmask]>

Reply-To:

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

Date:

Thu, 19 Apr 2007 12:36:22 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (161 lines)

Dear all,
changing the threshold value in featquery also does not solve the 
problem of incorrectly reported voxels. i was wondering if is there any 
way around this?
thank you very much for any help,
paymon


Paymon Hosseini wrote:
> Dear Steve ,
>
> I am having a similar problem. I am trying to find the % signal change 
> of several COPE files for one subject for a single voxel using 
> featquery. The featquery report uses the correct voxel for some COPE 
> files, and not for others.
>
> here is an example featquery output report:
> 1 stats/cope1 1 0.00 0.30 0.30 0.30 0.30 0.30 30 53 15 -2.45 57.30 
> 20.36 (correct voxel)
> 1 stats/cope2 1 0.00 0.36 0.36 0.36 0.36 0.36 30 53 15 -2.45 57.30 
> 20.36 (correct voxel)
> 1 stats/cope3 1 0.00 0.18 0.18 0.18 0.18 0.18 30 53 15 -2.45 57.30 
> 20.36 (correct voxel)
> 1 stats/cope4 1 -0.00 -0.00 -0.00 -0.00 -0.00 0.00 0 0 0 107.32 
> -107.92 -38.02 (incorrect voxel)
>
> for example in the above, stats/cope1 to stats/cope3 are evaluate at 
> the voxel i specified, but stats/cope4 is evaluate at some other voxel.
>
> Both the mask and the voxel are in standard space, and there are no 
> registration problems. All the cope images have an intensity value at 
> voxel i am interested in, when viewed in fslview. You said "if there 
> are no voxels above the threshold then the co-ordinates reported are 
> meaningless". what threshold are you referring to?
> Could you please explain in more detail why one cannot get a %signal 
> change (e.g stats/cope4 above), even though the stats/cope4.nii.gz has 
> a valid intensity value at the given voxel of interest?
>
> thanks
> paymon hosseini
>
>
>
>
> Steve Smith wrote:
>> Hi - yes, sorry, if there are no voxels above the threshold then the 
>> co-ordinates reported are meaningless - we'll get that fixed in the 
>> next release.
>> Cheers.
>>
>>
>> On 4 Apr 2007, at 00:24, Sang Lee wrote:
>>
>>> Hi Steve,
>>>
>>> The mask image was set to the standard space reference image used in 
>>> the registrations, and the mm coordinates were in the space of this 
>>> image. Also, there were no registration failure nor that the voxel 
>>> that I specified was outside the field-of-view-of the datasets.
>>>
>>> Possible that this error is generated when there is no real 
>>> activation in the voxel that I soecified? Looking at each 
>>> individuals that had these errors, all of them did not have any 
>>> activations in the specified voxel. i.e. no activation in the voxel 
>>> is generating these errors. If so, for these individuals, would it 
>>> be ok to assume that the mean % signal change is zero (for the % 
>>> signal change plot)?
>>>
>>> Thank you again for your help.
>>>
>>> From Sang
>>> Sang Lee
>>> Phenotype Genotype Project
>>> Athinoula Martinos Center for
>>> Biomedical Imaging
>>> 149 13th St. Rm. 2302
>>> Charlestown, MA 02129
>>> Fax:    617-726-1351
>>>
>>>
>>> On Apr 1, 2007, at 5:29 AM, Steve Smith wrote:
>>>
>>>> Hi - did you make sure that the mask image was set to the standard 
>>>> space reference image used in your registrations, and that the mm 
>>>> co-ordinates were in the space of this image? Also, is it possible 
>>>> that the registration had failed for the problematic FEAT runs, or 
>>>> that the voxel you specified was outside the field-of-view of those 
>>>> datasets?
>>>>
>>>> Cheers, Steve.
>>>>
>>>>
>>>> On 31 Mar 2007, at 21:37, Sang Lee wrote:
>>>>
>>>>> Dear FSL user,
>>>>>
>>>>> I am using PE files to calculate the percentage signal change via 
>>>>> featquery for a single voxel for
>>>>> each of my subjects (total n = 28).
>>>>>
>>>>> Given that I am using PE file,  an anatomical mask, and a mm 
>>>>> coordinate for a single voxel, using
>>>>> featquery tool with convert PE/COPE to % signal change option 
>>>>> turned on, I should get % signal
>>>>> change for each of my subjects for that single voxel.
>>>>>
>>>>> However, several of the subjects report file comes out with a 
>>>>> coordinate that I did not specify.
>>>>>
>>>>> For example, I specified (-16 -4 -16) for my mm coordinates. 
>>>>> However, several of my subjects'
>>>>> report file comes out with % signal change values with the 
>>>>> following coordinate (90 -126 -72).
>>>>> This happens with one third of my subjects. Is there something 
>>>>> that I am doing wrong? How do I
>>>>> deal with those results with the coordinates that I did not specify?
>>>>>
>>>>> I am trying to plot mean % signal change plot for all 28 subjects, 
>>>>> but I am not sure what to do with
>>>>> those subejct's mean % signal change that comes out with a 
>>>>> coordinate that I did not specify.
>>>>>
>>>>> Any input would be a great help!
>>>>>
>>>>> Thank you in advance.
>>>>>
>>>>> From Sang
>>>>
>>>>
>>>> --------------------------------------------------------------------------- 
>>>>
>>>> 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
>>>> --------------------------------------------------------------------------- 
>>>>
>>>
>>> The information transmitted in this electronic communication is 
>>> intended only for the person or entity to whom it is addressed and 
>>> may contain confidential and/or privileged material. Any review, 
>>> retransmission, dissemination or other use of or taking of any 
>>> action in reliance upon this information by persons or entities 
>>> other than the intended recipient is prohibited. If you received 
>>> this information in error, please contact the Compliance HelpLine at 
>>> 800-856-1983 and properly dispose of this information.
>>
>>
>> --------------------------------------------------------------------------- 
>>
>> 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