If this is your first contribution to the project, I would strongly
suggest to start by contributing a small bug fix or improvement to get
accustomed to the kind of things the core devs expect when reviewing a
PR.
Also please read the contributors guide :
http://scikit-learn.org/dev/developers/co
Hi,
Thank you all for the info. It is not my first contribution to a project (I
made little contributions to xgboost and tensorflow), even though I think it is
really interesting what Oliver said, specially because of the very curated
structure and guidelines of the project. BTW, I’ve found su
Yeah the input format is a bit odd, usually it should be n_samples x
n_features, so something like
[['A'], ['C'], ['T'], ['G']]
Though this is currently also hard to do :(
On 09/20/2016 05:50 AM, Lee Zamparo wrote:
Hi Joel,
Yea, seems that the one-hot encoding of the transpose solves the
iss
On 09/19/2016 09:56 PM, Nelle Varoquaux wrote:
Another bot-able tool might be pinging inactive PRs to ask if they're being
worked on, and labelling "Needs contributor" if there's no reply within n
days...!
That kind of only works when the status is "waiting for changes",
and not "waiting for r
On 21 September 2016 at 22:13, Andreas Mueller wrote:
>
>
> On 09/19/2016 09:56 PM, Nelle Varoquaux wrote:
>>>
>>> Another bot-able tool might be pinging inactive PRs to ask if they're
>>> being
>>> worked on, and labelling "Needs contributor" if there's no reply within n
>>> days...!
>
> That kin
