JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for SPM Archives


SPM Archives

SPM Archives


SPM@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

SPM Home

SPM Home

SPM  2005

SPM 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: normalization of limited slices

From:

John Ashburner <[log in to unmask]>

Reply-To:

John Ashburner <[log in to unmask]>

Date:

Mon, 25 Jul 2005 12:31:56 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (39 lines)

> We have acquired 6 slices of ASL images and wish to normalize.  We
> coregister these and a structural scan to a whole brain EPI acquired at
> the same sitting. 2 questions,
> 1) What is the better way to proceed, i) normalize the coregistered
> structural to the T1 template and apply _sn.mat to the coregisterd
> functional scans or  ii) normalize the EPI and apply _sn.mat to
> coregistered functional scans, or is there no difference?

There is likely to be a difference - but the better option may be difficult to 
predict.  One of the main factors relates to how much distortion you have in 
your EPI data.  If it is very distorted, then a good registration with the 
structural scan may not be possible - in which case any spatial normalisation 
parameters derived from the structural won't be especially accurate when 
applied to the EPI.  Other factors are the contrast and artifacts in your 
data.  Because spatial normalisation relies on minimising the mean squared 
difference between an image and template, then the contrast in the data 
should be similar for optimal results.


> 2) if / when normalizing the coregistered structural do we select the r*
> image or  the original structural,  - in light of previous posting [Re:
> normalization of few slices,Mon, 4 Dec 2000 15:26:50 +0000 (you don't
> need to use the r* image created by coregistration, as the
> coregistration transformation is added to the structural MRI .mat file)]?

Select the original image (where the relative orientation is encoded by the 
.mat file). If you try the Check Reg button with the original data after 
coregistration, then you should see that these are also in register.  This is 
done via the .mat files, rather  than by reslicing the data themselves.

The reason for chosing the original image is that resliced images sometimes 
contain regions where there is no data in the original image.  These are 
assigned a value of zero, which the spatial normalisation would try to 
distort because there would be no corresponding zero regions in the template 
image.

Best regards,
-John

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
2000
1999
1998


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