Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

max_time_mins doesn't work when use_dask=True in TPOT 0.9.5 #797

Open
weixuanfu opened this issue Nov 13, 2018 · 6 comments
Open

max_time_mins doesn't work when use_dask=True in TPOT 0.9.5 #797

weixuanfu opened this issue Nov 13, 2018 · 6 comments
Labels

Comments

@weixuanfu
Copy link
Contributor

Thank Mehroz Alam for reporting this issue via email. The max_time_mins parameter doesn't work when use_dask=True in TPOT 0.9.5. I will fix this bug and merge to dev branch first.

@weixuanfu
Copy link
Contributor Author

The PR #798 was just merged with a patch. If you want to try the dev branch, the command below can be used for installing dev branch to your environment:

pip install --upgrade --no-deps --force-reinstall git+ https://github.com/EpistasisLab/tpot.git@development

@Mehroz01
Copy link

Sir Weixuan Fu ,

I think max_eval_time_mins(to evaluate single pipeline ) is not working when we are using dask .
TPOT version 0.9.6

@weixuanfu
Copy link
Contributor Author

Hmm, somehow the timeout argument is not working with dask. I will look into it.

@Mehroz01
Copy link

OK Sir.

@s-marton
Copy link

s-marton commented Jun 2, 2019

Are there any news on max_eval_time_mins with dask?

@LizzAlice
Copy link

Are there any news in 2022?

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

No branches or pull requests

4 participants