I haven’t looked at Ruby in a long time. I do wonder what people mean by
PORTING to another language or environment that already has their own way of
doing things.
I did most of my recent work in native R enhanced by packages and have been
learning how to do similar things in modules on to
SciPy 2019, the 18th annual Scientific Computing with Python conference,
will be held July 8-14, 2019 in Austin, Texas. The annual SciPy Conference
brings together over 800 participants from industry, academia, and
government to showcase their latest projects, learn from skilled users and
developer
There's some stuff already:
https://github.com/SciRuby/
And in terms of strategy:
No, you can go estimator by estimator and at some point implement
cross-validation and grid-search and pipelines and metrics pretty
independently.
It looks like daru is written in ruby which I expect to be too s
If you count things in Scipy and NumPy (and Joblib and Cython?) that
Scikit-learn depends on and which may be lacking or hard to find
in SciRuby, it's much much more than 39 years. PyCall, and potentially some
Scikit-learn-specific wrappers around it, seems a much more sensible
approach.
__
Hi Andreas,
The person.year input is very valuable. This is a also the kind of
information I was looking for. The language would be Ruby. Now, it's true
that Ruby can already benefit from Scikit-learn through the PyCall
extension...
The point in my first question was also around the porting strat
