Great. Thanks.
On Mon, Sep 21, 2015 at 8:16 PM, Andreas Mueller wrote:
> This is something I have wanted to fix for a while, and which I'll do
> after the release and after the model_selection refactoring is merged.
>
>
>
> On 09/20/2015 05:02 PM, Artem wrote:
>
> You can't get validation part o
This is something I have wanted to fix for a while, and which I'll do
after the release and after the model_selection refactoring is merged.
On 09/20/2015 05:02 PM, Artem wrote:
You can't get validation part of current CV split in estimator either way.
On Sun, Sep 20, 2015 at 10:11 PM, okek p
You can't get validation part of current CV split in estimator either way.
On Sun, Sep 20, 2015 at 10:11 PM, okek padokek
wrote:
> So you are suggesting to pass the validation set as a parameter to the
> __init__() of the estimator? But how do I get the current validation set
> from GridSearchCV
So you are suggesting to pass the validation set as a parameter to the
__init__() of the estimator? But how do I get the current validation set
from GridSearchCV? Using my above code, do you mean something like this:
my_model = MY_MODEL()
pipe = Pipeline(steps=[("imputer", imputer), ("scaler", sca
Hi
Don't pass any parameters to fit method. Current API assumes that you set
all the parameters in estimator's constructor (__init__ method). It's a bit
nasty to set validation set during construction stage, but there's no
better approach.
On Sun, Sep 20, 2015 at 3:47 PM, okek padokek
wrote:
>
Hello,
I am trying to implement my own estimator. It currently seems to be
working. My fit() function is of the form
def fit(self, X, y=None):
# iteratively tune the params
return self
I would like to modify my fit() so that it can print out validation costs
as it itera
