Skip to content

WIP Modifying nmf.py for accepting mini-batches #13386

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

Closed
wants to merge 19 commits into from

Conversation

pcerda
Copy link

@pcerda pcerda commented Mar 4, 2019

Reference Issues/PRs

#13308

What does this implement/fix? Explain your changes.

Modification of the NMF class to accept mini batches. For the moment, it works only with
solver='mu' and beta_loss='kullback-leibler.

I also added the benchmark code.

Any other comments?

@pcerda
Copy link
Author

pcerda commented Mar 4, 2019

Result of the benchmark in a training set of size 500k. The loss is calculated on 10k test samples
screenshot from 2019-03-04 18-44-41

@pcerda
Copy link
Author

pcerda commented Mar 4, 2019

The advantage of the batch mode is that 'fit' calls 'fit_transform', so it automatically transforms the training data. This is not the case for the online method, so a 'transform' time should be considered

@GaelVaroquaux GaelVaroquaux changed the title Modifying nmf.py for accepting mini-batches WIP Modifying nmf.py for accepting mini-batches Mar 5, 2019
@amueller
Copy link
Member

amueller commented Aug 6, 2019

@pcerda are you still working on this?

@TwsThomas
Copy link
Contributor

I will try to pitch in.

@TwsThomas
Copy link
Contributor

I'm currently working on something else.
I will not (neither @pcerda) finish this PR (at least for this coming weeks).
You might consider this PR stalled.

@cmarmo
Copy link
Contributor

cmarmo commented Apr 17, 2020

Working on it in #16948.

@cmarmo cmarmo added the Superseded PR has been replace by a newer PR label Aug 29, 2020
Base automatically changed from master to main January 22, 2021 10:50
@thomasjpfan
Copy link
Member

I am closing this PR because #16948 is merged which includes the proposed feature.

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

Successfully merging this pull request may close these issues.

7 participants