Closed msluszniak closed 1 year ago
@msluszniak On the note of solvers, it may be useful to look at the implementations in jaxopt! JAX also supports LBFGS out of the box I believe, but the XLA version is significantly slower than the SciPy version
@seanmor5 do you solvers should be in a separate library then? Or here is fine?
Some additional thoughts:
Splitting data may also be worth moving to Nx, since it will be shared by both Scholar and Axon. So I would postpone tackling this for now
We most likely cannot implement training of decision trees - this poses the question if this library should implement decision trees in the first place. However, the HummingBird project shows it can be efficient to compile trained decision trees into tensors
@josevalim I think having the solvers in here is fine to start, and then if it grows too large it makes sense to pull them out. It may even make sense to combine the optimization stuff in Axon with the solvers implemented in Scholar if they eventually get pulled into a separate library, as the optimizers are more general purpose than just NNs
@msluszniak Is this priority list updated?
@msluszniak Is this priority list updated?
@tiagodavi I think that this list is still up to date. But of course, any contribution will be great :)
Is anyone working on SVM? What about saving/loading fitted models? I've got both in my near-term roadmap at work and can jump on them if they're not being worked on already.
@msluszniak is working on SVM. :)
Closing this for now in favor of smaller issues.
This issue presents the roadmap of the most important functionalities that should be implemented in the first place.