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

SPM July 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Registration trouble when I don't have full-brain coverage

From:

"Neggers, S.F.W." <[log in to unmask]>

Reply-To:

Neggers, S.F.W.

Date:

Wed, 15 Jul 2009 10:12:51 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (81 lines)

Dear Jonathan, cc List,

I did something similar with even smaller (midbrain) FOV, and had
registration issues as well.

My solution: get 1 whole brain EPI volume (eg, same sequence as your 1s
timeseries data, only with more slices and a correspondingly adapted
flip angle) right after functional scanning, and take graet care you
angulate this image exactly the same as your 14 slice functional time
series scans (eg only translate your FOV, do NOT change the angles). By
doing so your EPI distortion is nearly identical to your time series
data.

This whole brain EPI will likely register well with your time series
data, as it is exactly the same contrast, and has the same spatial EPI
distortions.

You could now do 2 things for registration with anatomy:

1. Coregister this whole brain EPI to your T1, choose time series as
'other' (after you registered your whole brain EPI to your timeseries).
This requires that your EPI has minimal spatial distortions, which is
usually an issue. Especially as you are focussing on OFC. Consider
acquiring both phase and magnitude images for phase unwarping your EPI
images.

2. Forget about registering to T1, and use whole brain EPI directly for
normalizing your time series to an EPI template. Depending on your image
contrast and the required spatial accuracy of the results, you could
even use 'unified segmentation' for this, but be sure you can reasonably
segment this whole brain EPI. For that, you might want to record 10
whole brain EPIs or so, and average them, for better image SNR.

Good luck,

Bas



--------------------------------------------------
Dr. S.F.W. Neggers
Division of Brain Research
Rudolf Magnus Institute for Neuroscience
Utrecht University Medical Center
Visiting : Heidelberglaan 100, 3584 CX Utrecht
          Room B.01.1.03
Mail    : Huispost B.01.206, P.O. Box 85500
          3508 GA Utrecht, the Netherlands
Tel      : +31 (0)88 7559609
Fax      : +31 (0)88 7555443
E-mail  : [log in to unmask]
--------------------------------------------------

 

> -----Oorspronkelijk bericht-----
> Van: SPM (Statistical Parametric Mapping) 
> [mailto:[log in to unmask]] Namens Jonathan Malmaud
> Verzonden: woensdag 15 juli 2009 9:07
> Aan: [log in to unmask]
> Onderwerp: [SPM] Registration trouble when I don't have 
> full-brain coverage
> 
> Hi,
> I am having trouble registering and normalizing fMRI data 
> that was gathered using a sequence with an RT of 1s 
> consisting of only 14 slices centered on the OFC in four subjects. 
> Normally I use 44 slices to cover the whole brain and 
> normalize my data by taking the mean of a subject's 
> functional scans and warping it to a EPI template. However, 
> this procedure is failing badly now that I only have coverage 
> of a small area of the brain. 
> Registration between a subject's functional scans and 
> T1-weighted anatomical scan is also giving poor results. Does 
> anyone have any advice on how to achieve usable registration results?
> 
> Much appreciated,
> Jon Malmaud
> California Institute of Technology
> 

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager