Skip to content
This repository has been archived by the owner on Oct 14, 2018. It is now read-only.

Support lazy evaluation #19

Closed
mrocklin opened this issue Feb 21, 2017 · 2 comments
Closed

Support lazy evaluation #19

mrocklin opened this issue Feb 21, 2017 · 2 comments

Comments

@mrocklin
Copy link
Member

I was trying to see the graph produced by DaskGridSearchCV.fit. My first attempt was to add a compute=False keyword. Looking at the code it's not clear that this is possible. Is this difficult to support?

@jcrist
Copy link
Member

jcrist commented Feb 21, 2017

Lazy evaluation conflicts with scikit-learn's api, and is tricky to support here in a way that is both intuitive and robust. For some configurations there is also the need to call get multiple times, which prevents lazy evaluation.

After calling fit, both the graph and the keys are stored on the grid search object as dask_graph_ and dask_keys_. You can also use the visualize method on the search object to view the graph:

>>> est.fit(X, y)
>>> est.visualize()

@mrocklin
Copy link
Member Author

Oh great. Thanks for the explanation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants