New funding for MNE software development

Dear all,

This week we were happy to receive from the National Institutes of Health (NIH) the initial Notice of Award of our new R01 grant ? Scalable Software for Distributed Processing and Visualization of Multi-Site MEG/EEG Datasets?. This project, funded by the National Institute of Neurological Disorders and Stroke (NINDS), will support the development of the MNE-Python software for the next four years. The two performance sites will be Massachusetts General Hospital (MGH, Dr. Matti H?m?l?inen, PI) and University of Washington (Dr. Samu Taulu). In addition, Dr. Alexandre Gramfort (INRIA, France), the initiator of the Python version of the MNE software will continue to act as a consultant in the project. Drs. Eric Larson at UW and Sheraz Khan at MGH will also contribute to the project.

For the past 8 years the MNE software has been developed in collaboration with Brainstorm under the auspices of a shared NIH grant. When we were charting our way forward in the development of the MNE and Brainstorm software packages, we realized that best strategy is to pursue two closely coordinated projects. We are, therefore very happy that the Brainstorm team was able to secure its own NIH funding as well. This will allow cross-fertilization of MNE and BrainStorm to continue and will allow the users benefit from the synergy between MNE and Brainstorm.

The continued development of MNE-Python will include:

1. System-independent automatic MEG/EEG data preprocessing

To harmonize preprocessing and to facilitate automatic processing of large data sets we will:

(i) Create a suite of noise cancellation tools incorporating and extending methods present in different MEG systems
(ii) Implement and validate methods for head-movement determination and compensation; and
(iii) Develop methods for automatic tagging of artifacts using machine learning approaches.

2. Distributed computing and interactive remote visualization

Complete processing of MEG/EEG data from a single subject on a modern desktop can take hours. We will leverage packages from the vibrant scientific Python ecosystem to offer seamless integration with both local and cloud-based computing clusters. We will also develop remote interactive visualization tools for raw and processed data.

3. Software development and dissemination

We will continue the multi-site development of MNE-Python enabled by GitHub using the best available programming practices to ensure multi-platform compatibility. We will also develop and maintain CentOS community images for Amazon Elastic Compute Cloud (EC2) and Google Compute Engine (GCE) to make it easy for MNE-Python users to employ these resources for their data analyses. We will continue to provide extensive web-based documentation, training and forums, and hands-on training workshops for users and developers.

We are very excited about this opportunity to add functionality to MNE-Python and look forward to working with existing and new users of the package to optimize the solutions for practical needs.

Best,
Matti H?m?l?inen, Samu Taulu, Eric Larson, Sheraz Khan & Alex Gramfort

External Email - Use Caution

Hi Matti et al.,

That's fantastic news! Congratulations!

Best,

Hari

External Email - Use Caution

Congratulations to you all MNE wizards, these are great news for the
community!

Best wishes,
Virginie

Virginie van Wassenhove
*https://brainthemind.com/*

External Email - Use Caution

Dear Matti and everyone involved,

Congratulations.
Our effort and I?m sure many times many others? efforts have been enabled by your essential and extraordinarily collaborative contributions.
I wish you all success in your continuing efforts.

Best - Don

[Signature0001]
Don Krieger, Ph.D.
Research Scientist
Department of Neurological Surgery
University of Pittsburgh
(412)648-9654 Office
(412)521-4431 Cell/Text

Thanks to everyone for the congratulations!

One strong aspect of our proposal was certainly the genuine enthusiasm of our user base, witnessed by the strong letters of support, which we are very grateful for. Despite of this, one of the reviewers still found it difficult to tell how widely the package is used! It might be interesting for you to read our evidence-based response in the rebuttal letter:

"The nationwide and worldwide impact and importance of MNE-Python is, indeed, exemplified in the 25 letters of support. In addition, we were easily able to identify over 20 NIH grants employing MNE-Python in their data analyses. Perhaps most importantly, MNE-Python and MNE-C are undergoing a large growth in terms of users. We can roughly quantify this using the total number of citations to the papers about these packages; the 180 citations in 2017 amounted to a 73% year-over-year increase from 2016, far outpacing the next fastest-growing MEG/EEG package (Brainstorm with 36%). This growth is attributable to two factors: the quality of the MNE software package itself, and to simultaneously increasing momentum of the scientific Python ecosystem.?

Cheers,
Matti

Dear MNE-Python team,

when following your instructions to install mne-python, one ends with a
conda environment which hosts the concurrent version of mne-python. This
works great!

However, after some time of usage one may wish to update this
installation to keep track with the most recent developments. One
solution would be to setup a new conda environment, of course, following
your instructions. I adopted the instructions to download the last
stable version 0.17:

$ curl -O
https://raw.githubusercontent.com/mne-tools/mne-python/maint/0.17/environment.yml

$ perl -pe 's/name:\s+mne/name: mne_v017/' environment.yml
>environment_v017.yml

$ conda env create -f environment_v017.yml

$ conda activate mne_v017

The other solution might be to follow your instructions under "advanced
setup". But something should be done differently than explained if I
want to update the version 0.17 while staying in this version. The
following command reported that it uninstalled v0.17 and updated to
v0.18dev:

$ pip install --upgrade --no-deps
git+https://github.com/mne-tools/mne-python.git

I also tried this (as recommended in the "advanced setup":

$ git clone git://github.com/mne-tools/mne-python.git

But, this creates a local directory mne-python which completely ignores
the existing conda environment. So, it is a different track.

Do you have recommendations for an effective updating strategy of an
existing conda environment?

Thank you and all the best,

Burkhard

External Email - Use Caution

I also tried this (as recommended in the "advanced setup":

$ git clone git://github.com/mne-tools/mne-python.git

But, this creates a local directory mne-python which completely ignores
the existing conda environment. So, it is a different track.

Did you do all three of the commands
<https://www.martinos.org/mne/stable/advanced_setup.html&gt;, namely:

git clone git://github\.com/mne\-tools/mne\-python\.git cd mne-python
$ python setup.py develop

The command `python setup.py develop` (while in the `mne-python` directory)
should install the `git` version to your environment over the
`pip`-installed stabel one. If it does not for some reason (?), then you
can equivalently do `pip install -e .` and `pip` should take care of
uninstalling the stable MNE and then installing in editable mode the dev
version.

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190123/ea732173/attachment-0001.html

Hi Eric,

many thanks for your quick answer. No, I did not try all three commands
together. I had stopped after the first. So, I repeated the first
command again:

$ git clone git://github.com/mne-tools/mne-python.git

<http://github.com/mne-tools/mne-python.git&gt;|

However, then I created a local branch for version 0.17, since I wanted
to update this version with the recent bug-fixes. Or is this plan a
complete waste of time, because 0.17 does not change anymore?

cd mne\-python git branch local.v017 remotes/origin/maint/0.17 $ git

checkout local.v017 |

And finally, I ran the python setup.py as recommended:

python setup.py --verbose develop |

And this seems to be successful although it shows a number of warnings?
Would you agree?
Thank you and best wishes,
Burkhard

running develop running egg_info creating mne.egg-info writing

mne.egg-info/PKG-INFO writing dependency_links to
mne.egg-info/dependency_links.txt writing top-level names to
mne.egg-info/top_level.txt writing manifest file
'mne.egg-info/SOURCES.txt' reading manifest file
'mne.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in'
warning: no previously-included files found matching 'conftest.py'
warning: no previously-included files matching '*' found under directory
'examples/MNE-sample-data' warning: no previously-included files
matching '*' found under directory 'examples/MNE-testing-data' warning:
no previously-included files matching '*' found under directory
'examples/MNE-spm-face' warning: no previously-included files matching
'*' found under directory 'examples/MNE-somato-data' warning: no
previously-included files found matching 'Makefile' warning: no
previously-included files found matching '.coveragerc' warning: no
previously-included files found matching '*.yml' warning: no
previously-included files found matching 'ignore_words.txt' warning: no
previously-included files found matching '.mailmap' warning: no
previously-included files matching '*.pyc' found under directory 'mne'
warning: no previously-included files matching '*' found under directory
'doc' warning: no previously-included files matching '*' found under
directory 'logo' warning: no previously-included files found matching
'CODE_OF_CONDUCT.md' warning: no previously-included files found
matching '.github' warning: no previously-included files found matching
'.github/CONTRIBUTING.md' warning: no previously-included files found
matching '.github/ISSUE_TEMPLATE' warning: no previously-included files
found matching '.github/ISSUE_TEMPLATE/blank.md' warning: no
previously-included files found matching
'.github/ISSUE_TEMPLATE/bug_report.md' warning: no previously-included
files found matching '.github/ISSUE_TEMPLATE/feature_request.md'
warning: no previously-included files found matching
'.github/PULL_REQUEST_TEMPLATE.md' warning: no previously-included files
matching '*' found under directory 'mne/io/tests/data' warning: no
previously-included files matching '*' found under directory
'mne/io/bti/tests/data' warning: no previously-included files matching
'*' found under directory 'mne/io/edf/tests/data' warning: no
previously-included files matching '*' found under directory
'mne/io/kit/tests/data' warning: no previously-included files matching
'*' found under directory 'mne/io/brainvision/tests/data' warning: no
previously-included files matching '*' found under directory
'mne/io/egi/tests/data' warning: no previously-included files matching
'*' found under directory 'mne/io/nicolet/tests/data' warning: no
previously-included files matching '*' found under directory
'mne/preprocessing/tests/data' writing manifest file
'mne.egg-info/SOURCES.txt' running build_ext Creating
/scr/kuba1/miniconda3/envs/mne_v017/lib/python3.6/site-packages/mne.egg-link
(link to .) Adding mne 0.17.0 to easy-install.pth file Saving
/scr/kuba1/miniconda3/envs/mne_v017/lib/python3.6/site-packages/easy-install.pth
Installing mne script to /scr/kuba1/miniconda3/envs/mne_v017/bin
changing mode of /scr/kuba1/miniconda3/envs/mne_v017/bin/mne to 775
Installed /nobackup/nigeria1/clozep/mne-python Processing dependencies
for mne==0.17.0 Finished processing dependencies for mne==0.17.0running
develop running egg_info creating mne.egg-info error: [Errno 2] No such
file or directory |

???External Email - Use Caution

    I also tried this (as recommended in the "advanced setup":

    $ git clone git://github.com/mne-tools/mne-python.git
    <http://github.com/mne-tools/mne-python.git&gt;

    But, this creates a local directory mne-python which completely
    ignores the existing conda environment. So, it is a different track.

Did you do all three of the commands
<https://www.martinos.org/mne/stable/advanced_setup.html&gt;, namely:
> git clone git://github\.com/mne\-tools/mne\-python\.git &lt;http://github.com/mne-tools/mne-python.git&gt; cd mne-python $ python
setup.py develop |
The command `python setup.py develop` (while in the `mne-python`
directory) should install the `git` version to your environment over
the `pip`-installed stabel one. If it does not for some reason (?),
then you can equivalently do `pip install -e .` and `pip` should take
care of uninstalling the stable MNE and then installing in editable
mode the dev version.

Eric

_______________________________________________
Mne_analysis mailing list
Mne_analysis at nmr.mgh.harvard.edu
Mne_analysis Info Page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/43f894fd/attachment-0002.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4962 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/43f894fd/attachment-0001.bin
-------------- next part --------------
        External Email - Use Caution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/43f894fd/attachment-0003.html

External Email - Use Caution

However, then I created a local branch for version 0.17, since I wanted to
update this version with the recent bug-fixes. Or is this plan a complete
waste of time, because 0.17 does not change anymore?

We have pushed some fixes to `maint/0.17` and plan to release a minor
bugfix version 0.17.1 in the coming weeks. It's possible we will eventually
release a 0.17.2 if we find other critical bugs. 0.18 should come out
around May.

And this seems to be successful although it shows a number of warnings?

Would you agree?

If you do `python -c "import mne; mne.sys_info()" it should report its
version to you have, and `python -c "import mne; print(mne)"` will give you
the path it's using for the module, which for you should be something like:

<module 'mne' from '/nobackup/nigeria1/clozep/mne-python/mne/__init__.py'>

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/6764276e/attachment.html

thank you very much for these hints, Eric.

???External Email - Use Caution

    However, then I created a local branch for version 0.17, since I
    wanted to update this version with the recent bug-fixes. Or is
    this plan a complete waste of time, because 0.17 does not change
    anymore?

We have pushed some fixes to `maint/0.17` and plan to release a minor
bugfix version 0.17.1 in the coming weeks. It's possible we will
eventually release a 0.17.2 if we find other critical bugs. 0.18
should come out around May.

    And this seems to be successful although it shows a number of
    warnings? Would you agree?

If you do `python -c "import mne; mne.sys_info()" it should report its
version to you have, and `python -c "import mne; print(mne)"` will
give you the path it's using for the module, which for you should be
something like:
><module 'mne' from
'/nobackup/nigeria1/clozep/mne-python/mne/__init__.py'> |
Eric

_______________________________________________
Mne_analysis mailing list
Mne_analysis at nmr.mgh.harvard.edu
Mne_analysis Info Page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/2a305a4d/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4962 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/2a305a4d/attachment.bin
-------------- next part --------------
        External Email - Use Caution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20190124/2a305a4d/attachment-0001.html