Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ML Documentation: what's missing #4556

Open
6 tasks
kingjr opened this issue Sep 13, 2017 · 4 comments
Open
6 tasks

ML Documentation: what's missing #4556

kingjr opened this issue Sep 13, 2017 · 4 comments
Labels

Comments

@kingjr
Copy link
Member

kingjr commented Sep 13, 2017

Here is a proposal in the todo for the MVPA/Decoding-Encoding/ML module.

  • a brief tutorial on ML to introduce the key concepts (fitting, predicting, scoring, CV)
  • a tutorial on model interpretation and its limits: when can you do patterns, what does it mean, what are the risks
  • a tutorial to highlight the importance of supervised spatial filter for oscillatory activity
  • a tutorial to highlight importance of supervised spatial filters for various types of artefacts
  • a tutorial to do source decoding and its risks
  • a tutorial to explain pipeline with 2D, 3D, 4D tensors

Please comment and I'll update the proposal.

@agramfort
Copy link
Member

agramfort commented Sep 14, 2017 via email

@jasmainak
Copy link
Member

It's more an API thing but I get a lot of questions which basically boil down to using 3D data in pipelines leading to weird shape mismatches. I guess some estimators can be pipelined in sequence but others cannot be. This needs to be probably clarified.

@kingjr
Copy link
Member Author

kingjr commented Sep 14, 2017

do you have already materials for some of this?

Yes, in the form of ipynb for all of the above, but a bit too long as compared to the MNE tutorials. Shall I start opening PRs?

It's more an API thing but I get a lot of questions which basically boil down to using 3D data in pipelines leading to weird shape mismatches. I guess some estimators can be pipelined in sequence but others cannot be. This needs to be probably clarified.

Ok that's easy, we can dedicate a tutorial to pipeline. I think it is an important an concept, especially with our tensor-like data structure.

@agramfort
Copy link
Member

let's not make PRs but maybe make a repo of 3-4 notebooks with an index.ipynb like here:

https://github.com/jakevdp/PythonDataScienceHandbook/tree/master/notebooks

then we take the figures from the notebook for the paper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants