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

tune.grid_search() should accept iterables #25212

Closed
waleedkadous opened this issue May 26, 2022 · 0 comments · Fixed by #25220
Closed

tune.grid_search() should accept iterables #25212

waleedkadous opened this issue May 26, 2022 · 0 comments · Fixed by #25220
Assignees
Labels
bug Something that is supposed to be working; but isn't P2 Important issue, but not time-critical tune Tune-related issues

Comments

@waleedkadous
Copy link
Contributor

tune.grid_search() does not accept iterables (e.g. range(1,10)).

Thus

search_space = {"max_depth": tune.grid_search(range(1,12)) }

causes an error. I think many people would expect the above to work.

Instead the user has to write:

search_space = {"max_depth": tune.grid_search(list(range(1,12))) } 
@waleedkadous waleedkadous added bug Something that is supposed to be working; but isn't tune Tune-related issues triage Needs triage (eg: priority, bug/not-bug, and owning component) labels May 26, 2022
@krfricke krfricke added P2 Important issue, but not time-critical and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't P2 Important issue, but not time-critical tune Tune-related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants