<div dir="ltr">Yes, I think that is the best way to do it in the c-code<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 8, 2015 at 10:43 AM, Scott Marek <span dir="ltr"><<a href="mailto:smarek0502@gmail.com" target="_blank">smarek0502@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi all,<br></div><div><br>Note: This is still Natalie, replying from a friend's account
because I didn't get your response to my inbox yet (digest settings),
but I wanted to ask a follow up question.</div><div><br></div>I
want to confirm regarding the prior: when I have the group-level fMRI
prior in fsaverage space as a .w file, I should morph that to each
individual subject's space for use in mne_do_inverse_operator, correct?
(Using mri_surf2surf for instance...)<br><div><br></div><div>I will then
define labels on the fsaverage fMRI map and morph the labels to each
individual to when I want to extract source estimates for the labels.</div><div><br></div><div>Thank you,</div><div><br></div><div>Natalie</div><div><div><img src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 8, 2015 at 10:00 AM, dgw <span dir="ltr"><<a href="mailto:dgwakeman@gmail.com" target="_blank">dgwakeman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Natalie,<br>
<br>
IMO<br>
a modified version of option 1 is the best option. Morph the labels to<br>
the individual's space.<br>
<br>
Then, instead of morphing the later inverse solutions back to<br>
fsaverage, simply extract the data only from the group defined labels<br>
and run stats on the label data only. This strategy reduces the amount<br>
of morphing and fits your hypothesis that the fMRI labels contain the<br>
activity of interest (which the strong fMRI prior will make happen<br>
anyway). The subsequent morphing would not accomplish anything (except<br>
possibly introduce erroneous smoothing), because the labels are<br>
derived from the average space anyway, so each label is equivalent in<br>
the different participants.<br>
<br>
hth<br>
d<br>
<div><div><br>
On Thu, Oct 8, 2015 at 9:09 AM, Natalie Klein <<a href="mailto:neklein@andrew.cmu.edu" target="_blank">neklein@andrew.cmu.edu</a>> wrote:<br>
> Hello,<br>
><br>
> I want to use a group-level fMRI map (in fsaverage space) as an fMRI prior<br>
> for MNE source localization. I also want to define labels from the fMRI map<br>
> that can be used for all subjects.<br>
><br>
> Previously, I created source spaces for all subjects in each one's<br>
> individual anatomical space. I could not find any tools that allow me to<br>
> morph these source spaces to fsaverage before doing forward/inverse solution<br>
> - it seems most morphing procedures are designed to be applied after the<br>
> inverse solution. So it seems my options are:<br>
><br>
> 1. Use the individual source spaces for the forward solution. Morph the fMRI<br>
> prior to each subject's individual space to do the inverse solutions. Define<br>
> labels on group fMRI map and then morph labels to each individual space for<br>
> analysis (or tediously draw labels on each morphed fMRI prior map).<br>
><br>
> or<br>
><br>
> 2. Redo the source spaces: morph all subjects to fsaverage space with<br>
> mne_setup_source_space and perform forward/inverse solution and all<br>
> remaining analysis in fsaverage space.<br>
><br>
> Any advice or opinions on the best way to proceed? Option 2 seems best as<br>
> there is less morphing overall, but I would appreciate input/advice.<br>
><br>
> Thank you,<br>
><br>
> Natalie<br>
><br>
</div></div>> _______________________________________________<br>
> Mne_analysis mailing list<br>
> <a href="mailto:Mne_analysis@nmr.mgh.harvard.edu" target="_blank">Mne_analysis@nmr.mgh.harvard.edu</a><br>
> <a href="https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis" rel="noreferrer" target="_blank">https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis</a><br>
><br>
><br>
> The information in this e-mail is intended only for the person to whom it is<br>
> addressed. If you believe this e-mail was sent to you in error and the<br>
> e-mail<br>
> contains patient information, please contact the Partners Compliance<br>
> HelpLine at<br>
> <a href="http://www.partners.org/complianceline" rel="noreferrer" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you in<br>
> error<br>
> but does not contain patient information, please contact the sender and<br>
> properly<br>
> dispose of the e-mail.<br>
><br>
_______________________________________________<br>
Mne_analysis mailing list<br>
<a href="mailto:Mne_analysis@nmr.mgh.harvard.edu" target="_blank">Mne_analysis@nmr.mgh.harvard.edu</a><br>
<a href="https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis" rel="noreferrer" target="_blank">https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Mne_analysis mailing list<br>
<a href="mailto:Mne_analysis@nmr.mgh.harvard.edu">Mne_analysis@nmr.mgh.harvard.edu</a><br>
<a href="https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis" rel="noreferrer" target="_blank">https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis</a><br>
<br>
<br>
The information in this e-mail is intended only for the person to whom it is<br>
addressed. If you believe this e-mail was sent to you in error and the e-mail<br>
contains patient information, please contact the Partners Compliance HelpLine at<br>
<a href="http://www.partners.org/complianceline" rel="noreferrer" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you in error<br>
but does not contain patient information, please contact the sender and properly<br>
dispose of the e-mail.<br>
<br></blockquote></div><br></div>