I want to use smile but their license is prohibiting the use of it at my company. I understand the project authors' intentions to promote contributions to the project, but the requirements to get commercial license is a deal breaker for many.
This looks excellent, will take a bit of time to go through and understand. The announcement blog is really helpful actually and explains the problem you're solving well (and one I am intimately familiar with so I see value here).
We have a strong focus on provenance, Tribuo models capture their input and output domains, along with the necessary configuration to rebuild a model. Tribuo's also more object oriented, nothing returns a bare float or int, you always get a strongly typed prediction object back which you can use without looking things up. Tribuo is also happy to integrate with other ML libraries on the JVM like TensorFlow and XGBoost, providing the same provenance/tracking benefits as standard Tribuo models, and we contribute fixes back to those projects to help support the ecosystem. Plus we can load models trained in Python via ONNX.
To your direct question, I've not benchmarked Smile against Tribuo. We are very interested in the upcoming Java Vector API - https://openjdk.java.net/jeps/338 - targeted at Java 16, which will let us accelerate computations which C2 or Graal don't autovectorise.
[+] [-] craigacp|5 years ago|reply
[+] [-] stevehiehn|5 years ago|reply
[+] [-] bratao|5 years ago|reply
[+] [-] hakjink|5 years ago|reply
[+] [-] jarym|5 years ago|reply
Congratulations!
[+] [-] latenightcoding|5 years ago|reply
[+] [-] craigacp|5 years ago|reply
[+] [-] londogard|5 years ago|reply
What would you say differentiates you from Smile which includes a simplistic datagrame, visualisation and support for CBLAS etc.
Is speed on par?
[+] [-] craigacp|5 years ago|reply
To your direct question, I've not benchmarked Smile against Tribuo. We are very interested in the upcoming Java Vector API - https://openjdk.java.net/jeps/338 - targeted at Java 16, which will let us accelerate computations which C2 or Graal don't autovectorise.
[+] [-] suyash|5 years ago|reply
[+] [-] nikhilgk|5 years ago|reply
- What does the future road map look like?
- Are you planning on adding more algorithms ?
- Any plans to bring in dataset and dataframe handling capabilities such as in numpy/pandas etc?
- What other interop features with other languages/platforms are planned?
- Any plans for AutoML features?
[+] [-] SiempreViernes|5 years ago|reply
[+] [-] RocketSyntax|5 years ago|reply