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

ENH: decoding module 2017 #3442

Open
26 of 38 tasks
kingjr opened this issue Jul 20, 2016 · 7 comments
Open
26 of 38 tasks

ENH: decoding module 2017 #3442

kingjr opened this issue Jul 20, 2016 · 7 comments

Comments

@kingjr
Copy link
Member

kingjr commented Jul 20, 2016

This aims at keeping track of the development related to the Google summer of code 2016 on decoding analyses.

We have quite a lot ongoing PRs, so I thought I would try to organize them here to keep track of the big picture. I'll edit the post along the issue along the way.

The aim is to make transformers that follow the sklearn API:

pipe = make_pipeline(
    CSP(sfreq=200, None, 30),
    TimeFrequency(),
    SlidingEstimator(make_pipeline(StandardScaler(), LogisticRegression())
)

score = cross_val_score(X=epochs.get_data(), y=epochs.event[:, 2])

For now, we're focusing on sklearn integration, not high level features (plotting, get_coefs_ etc).

@kingjr kingjr changed the title ENH: GSoC 2016 ENH: decoding module 2016 Sep 9, 2016
@larsoner
Copy link
Member

@kingjr is this issue still the roadmap, or should we close?

@kingjr
Copy link
Member Author

kingjr commented Mar 21, 2017

Still rough roadmap, although needs to be updated. Let's close it after the sprint IMO.

@larsoner larsoner changed the title ENH: decoding module 2016 ENH: decoding module 2017 Mar 21, 2017
@kingjr
Copy link
Member Author

kingjr commented Mar 31, 2017

I'm actually for keeping it up ;)

@jona-sassenhagen
Copy link
Contributor

@kingjr , @agramfort 's idea is one which will result in rERP and the receptive field module staying separate forever.

  • rERP becomes restricted to the original idea, allowing only sparse predictors; dense predictors are handled by receptive field module
  • receptive field module should be extended slightly to simply also using sparse predictors
    (- XDawn and rERP should still be united)

@jona-sassenhagen
Copy link
Contributor

I closed/crossed out a few that had been done since.
8 issues still open.

@jona-sassenhagen
Copy link
Contributor

@kingjr any idea for an example for UnsupervisedSpatialFilter with the example data? The only thing I can think of is show that you can use an unregularized algorithm when p > n by reducing p in dimensionality via PCA, i.e., for the MEG data with many channels and few trials.

@kingjr
Copy link
Member Author

kingjr commented Aug 4, 2018 via email

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

No branches or pull requests

3 participants