[Mne_analysis] fmri spatial prior

[Eric Larson]

If you open an issue on the MNE-Python issue tracker and mention these use
cases, it's possible that someone will find time to do it.

Eric


On Tue, Sep 13, 2016 at 11:08 AM, GREGORY R KIRK <gkirk at wisc.edu> wrote:

> Hi Alex,
>
>
> So this functionality is still available in the c version ?
>
>
> we have a very interesting measure derived from fMRI data
>
> that we would like to establish the correspondence with electrical
>
> activity source localized over frequency bands. We are submitting a grant
>
> application with this as one of the aims. We have a very good research
> electrophysiologist
>
> in our group. The data we will be working with is simultaneously acquired
> eeg/fmri
>
> from UCL and possibly another site. Would there possibly be interest in
> collaborating to
>
> implement something sensible ?
>
>
> Best & thanks
>
>
> Greg
> ------------------------------
> *From:* mne_analysis-bounces at nmr.mgh.harvard.edu <
> mne_analysis-bounces at nmr.mgh.harvard.edu> on behalf of Alexandre Gramfort
> <alexandre.gramfort at telecom-paristech.fr>
> *Sent:* Tuesday, September 13, 2016 2:28:42 AM
> *To:* Discussion and support forum for the users of MNE Software
> *Subject:* Re: [Mne_analysis] fmri spatial prior
>
> Hi Greg,
>
> the python code does not implement fMRI weighting.
>
> that's what we have in the MNE-C doc:
>
> http://martinos.org/mne/stable/manual/source_localization/inverse.html?
> highlight=fmri#fmri-guided-estimates
>
> quote:
>
> "It turns out that the fMRI weighting has a strong influence on the
> MNE but the noise-normalized estimates are much less affected by it."
>
> as we recommend to use the noise-normalized estimates it has so far
> not been requested.
>
> Alex
>
>
> On Mon, Sep 12, 2016 at 7:40 PM, GREGORY R KIRK <gkirk at wisc.edu> wrote:
> > Hi folks,
> >
> >
> > seems i used to see some documentation for how to use an
> >
> > fmri spatial prior as a weighted constraint for the mne source
> >
> > modelling tools. Is such functionality available in the current version ?
> >
> >
> > thank you
> >
> >
> > Greg
> >
> >
> > _______________________________________________
> > Mne_analysis mailing list
> > Mne_analysis at nmr.mgh.harvard.edu
> > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis
> >
> >
> > The information in this e-mail is intended only for the person to whom
> it is
> > addressed. If you believe this e-mail was sent to you in error and the
> > e-mail
> > contains patient information, please contact the Partners Compliance
> > HelpLine at
> > http://www.partners.org/complianceline . If the e-mail was sent to you
> in
> > error
> > but does not contain patient information, please contact the sender and
> > properly
> > dispose of the e-mail.
> >
> _______________________________________________
> Mne_analysis mailing list
> Mne_analysis at nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis
>
> _______________________________________________
> Mne_analysis mailing list
> Mne_analysis at nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis
>
>
> The information in this e-mail is intended only for the person to whom it
> is
> addressed. If you believe this e-mail was sent to you in error and the
> e-mail
> contains patient information, please contact the Partners Compliance
> HelpLine at
> http://www.partners.org/complianceline . If the e-mail was sent to you in
> error
> but does not contain patient information, please contact the sender and
> properly
> dispose of the e-mail.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20160913/a066257a/attachment.html