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  October 2011

SPM October 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Question regarding coregistration in SPM8

From:

Vladimir Litvak <[log in to unmask]>

Reply-To:

Vladimir Litvak <[log in to unmask]>

Date:

Fri, 7 Oct 2011 08:24:16 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (91 lines)

Dear Vivek,

On Fri, Oct 7, 2011 at 3:15 AM, Buch, Vivek (NIH/NINDS) [G]
<[log in to unmask]> wrote:
> Hi Dr. Litvak,
> Thank you so much for the reply. I did indeed find this out because I realized that I can define my own nifti image as the sMRI input in the spm_eeg_inv_mesh function. However, in this function I am not asked to define the MEG fiducials or define the voxel-space for the T1 fiducials, which I somehow need to do.
>

See below

> I understand what you are saying about coregistering the subject T1 to the SPM template. But I feel that for our purposes I might >prefer to coregister the subject MEG to the subject T1 directly if possible, so that we get the best anatomical representation of >source space for the DCM.

Coregistering an image to the template will not affect the 'anatomical
representation of the source space'. It is not the same as
normalisation. If your images are slightly off it will be OK, but if
they are, for instance rotated with respect to the template, you won't
be able to use them in SPM so this is something you must check and fix
if necessary.


> I just failed to mention in the previous email, but we do get the same 3 fiducials coordinates in MEG space via CTF, as a .res4 file > within our .ds file.
>

Not sure what you mean, but it's not enough if can just read the
fiducial coordinates off the screen. They must be in the dataset in
the particular representation that we use so you should follow the
instructions from the previous e-mail.


> Ideally, I would like to write a script to be able to batch the coregistration of each subject's MEG sensor space to their own T1 image over all of our subjects, and would therefore actually prefer to use the matlab functions rather than the GUI. I know this would be possible to do, but am just having difficulty with the details! I think I may need to use a combination of the spm_eeg_prep and spm_eeg_inv_mesh functions--but cannot figure out exactly how to define the MEG.res4 fiducial file, T1 voxel coordinates, and T1 nifti image within those matlab functions to be able to coregister the subject MEG space to the subject T1 space to create an accurate head model for each subject. Would you be able to recommend a course of action?
>

You should look at the SPM batch tool. There is a tool for 'head-model
specification' there. Once you make it work for your data you can do
'Save as...' and choose '.m' file. This will generate the
corresponding Matlab code that you can put in your script, add the
line

spm_jobman('run', matlabbatch);

and you are ready to go.

> Thank you so much, I am very sorry to bother you on this subject.

You are not bothering me at all. It's part of my job to answer
questions. However, I'd prefer that you send questions of general
interest to the SPM mailing list ([log in to unmask]).

Best,

Vladimir

>
> Best,
> Vivek
>
> ________________________________________
> From: Vladimir Litvak [[log in to unmask]]
> Sent: Thursday, October 06, 2011 7:10 PM
> To: Buch, Vivek (NIH/NINDS) [G]
> Cc: [log in to unmask]
> Subject: Re: Question regarding coregistration in SPM8
>
> Dear Vivek,
>
> What you are overlooking is that nifti format is the native format of SPM so there is no need to convert it at all. What you should make sure is that your images are roughly aligned to SPM template or it might be a good idea to coregister and reslice them to the template using functionality in fMRI part of SPM. Then you can just press the MRI button and select your coregistered image.
>
> There is a different issue that might trouble you. You need fiducials for SPM coregistration and these are not present in Fieldtrip data. You can look at example script in man/example_scripts to see how you can add them, or there is also a tool in MEEGtools toolbox for that (Copy MEG sensors).
>
> Best,
>
> Vladimir
>
>
>
> On 6 Oct 2011, at 21:59, "Buch, Vivek (NIH/NINDS) [G]" <[log in to unmask]<mailto:[log in to unmask]>> wrote:
>
> Hi Dr. Litvak,
> My name is Vivek and I am a new research fellow at the NIH conducting cortical plasticity research using MEG. I am very interested in using DCM to start modeling effective connectivity graphs in my data. However, I am having trouble with the preparation. I have preprocessed the MEG data in fieldtrip (we collect MEG using CTF) and converted to spm format. However, I am having trouble with the coregistration process. I have standard NA, LPA, and RPA fiducial coordinates in voxel space for each subject’s T1 scan. The scan format is nifti (.nii). I need to coregister the MEG sensor space to the nifti T1 space for each subject, but I can’t figure out how to get the .nii format converted to either .mri or some other format that is readable by SPM. I have tried looking into fieldtrip tools but their ft_volumerealign does not recognize .nii files. Is there something I am overlooking, or are there other ways for me to go about doing this?
>
> Very sorry to bother you, thank you very much for your help.
>
> Best,
> Vivek
>
> Vivek P. Buch, MD Candidate
> HHMI-NIH Research Fellow
> National Institutes of Health, Bethesda, MD
> Warren Alpert Medical School of Brown University, Providence, RI
>

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