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  June 2014

SPM June 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: When do artifacts prevent proper coreg/normalize

From:

Helmut Nebl <[log in to unmask]>

Reply-To:

Helmut Nebl <[log in to unmask]>

Date:

Thu, 5 Jun 2014 17:49:04 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (20 lines)

Dear Ananth,


I'd say segmentation for 1) VBM and 2) for normalisation purpose are two different issues. Anatomical volumes might be sufficient for preprocessing aspects but "too bad" for VBM at the same time, although I don't know of any "rules" or guidelines. Reviewers might have a different opinion of course, but here some subjective thoughts:

1) If you want to conduct VBM then any artefact (like the ringing) is going to bias / lower the quality of VBM to some extent, at least locally. Often it is also problematic because artefacts might be more frequent in one group (e.g. head motion in patients), so differences in grey matter might actually be differences in data quality. In a strict way you would have to exclude any of these volumes, as there are visible artefacts and thus they probably don't meet your expectations. However, this is rather difficult when it comes to volumes with e.g. lower SNR overall. The VBM8 toolbox has an option to detect outlier volumes based on sample homogenity, thus providing some objective criterion. It's a little tricky of course and you should still check the data yourself, as volumes with clear and possibly severe local artefacts might still be within the "normal" range and other volumes with good data quality but maybe some anatomical anomalies (e.g. large sinuses in healty or maybe large atrophy in patients) might fall outside. To avoid any confusion due to differences in head structures like the neck you might test the sample homogenity of the skull-stripped versions (or c1* for VBM).

2) For segmentation-based normalisation the data quality should be less important, as you're just interested in the normalisation part. As far as I remember some smoothing is applied during coregistration, so artefacts like the ringing should actually be of a minor issue here. The coreg is not perfect anyway due to its nature (between-modality registration of two images with quite different resolutions, different geometric distortions, different dropouts) and manual adjustments might be necessary, especially if you don't cover the entire cortex during the EPI session. In that case the structure might be shifted a few mm too much along z after coreg. I once played with some animal fMRI data with extreme dropouts in the EPIs, the automatic coregistration was worthless in that case. So just try, also with the motion-corrupted volumes, and then check the outcome.

Concerning the segmentation itself, I'm not sure about the data in your case, but with motion-corrupted volumes the border between grey and white matter is typically very blurry. Voxels are going to be misclassified based on the intensity then, but the normalisation part / deformations tends to be okay in my experience (although this is a subjective impression of course). But make sure this holds for your data as well.

In any case you should definitely use the same preprocessing pipeline within a study. The different normalisation options (segmentation-based, T1 template, EPI template) lead to somewhat different outcomes, also concerning the global shape, even if we regard all of them as MNI space afterwards. In my opinion EPI template normalisation is equivocal to some extent anyway, as the distortions and signal dropouts might be quite different in your raw data compared to the template, and the distortions might also vary between subjects depending on slice positioning. For example if you have large dropouts in ventromedial frontal cortex, then the more dorsal aspects might (incorrectly) be warped downward. Same holds true if you don't cover the entire cortex due to limitations from slice thickness * number of slices. Assume the topmost part of the cortex was outside the filed of view. With EPI normalisation the covered parts are going to be warped out-/upwards to some extent, and your normalised data might look as if you've covered the whole brain.

Thus, if the segmentation or T1 template normalisation does not work well for your bad volumes, either turn to mean to EPI template normalisation for the whole study  or discard the functional series of affected subjects (or try to rescan these subjects). Typically the data loss shouldn't be that dramatic as subjects with lots of head motion during the anatomical scan probably move around during the (much more disturbing) EPI session a lot as well.


Hope this helps a little,

Helmut

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