…
From: scikit-learn On
Behalf Of Andreas Mueller
Sent: Tuesday, February 5, 2019 11:40 AM
To: scikit-learn@python.org
Subject: Re: [scikit-learn] Scikit-learn porting strategy
There's some stuff already:
https://github.com/SciRuby/
And in terms of strategy:
No, you can go estimator by esti
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
Hi Eljay.
Which language? And you want to reimplement it? How many full-time
developers do you have for how many year? ;) Openhub estimates
scikit-learn took 39 person-years:
https://www.openhub.net/p/scikit-learn/estimated_cost
I'm asking about the language because there are similar projects
Hi everyone,
If one were to start porting scikit-learn to another language what would be
the plan to follow? I'm looking for directions that would say something like
a) start with foundational components (e.g. numpy I guess)
b) then port module A for a quick win,
c) follow with modules B, C...
d)
