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

skorch #4

Open
pfistfl opened this issue Nov 26, 2019 · 3 comments
Open

skorch #4

pfistfl opened this issue Nov 26, 2019 · 3 comments

Comments

@pfistfl
Copy link
Member

pfistfl commented Nov 26, 2019

Should really look at skorch.readthedocs.io. I think this has many things we might want!

@JackyP
Copy link

JackyP commented Nov 28, 2019

Hello - skorch is awesome in Python but is anyone able to run torch in reticulate with Rstudio? I recently tried it and ran into rstudio/reticulate#273

I'm interested to write an mlr3 wrapper for fast.ai and its bag of tricks including a tabular learner but did not get very far due to that.

@pfistfl
Copy link
Member Author

pfistfl commented Nov 28, 2019

Hey, nice to see someone looking into this!

I looked at this for a bit earlier this year, (basically also looking into fast.ai tabular learners) and did not get very far as well.
I then started re-writing some of the fast.ai things for keras (i.e. the learning rate range test etc.).

I haven't looked too deep into actually directly calling fast.ai functions (which would be cool).
I guess this would mainly require to convert R's data.tables into some pd.DataFrame that works with fast.ai?

@pfistfl
Copy link
Member Author

pfistfl commented Nov 28, 2019

Just from the top of my head, what I would like to have from fast.ai that is currently not available in mlr3keras:

  • cyclical learning rates
  • learning rate range test
  • tabular preprocessing stuff (this should go into mlr3pipelines)
  • callbacks for model debugging
  • fit_one_cycle etc.
  • modern optimizers / initializers

Any other thoughts?
I feel porting architectures between pytorch and keras should not be such a big issue.

If we can talk to fast.ai via reticulate and that all goes smoothly, this would be an optimal outcome I guess :)

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

2 participants