-
Notifications
You must be signed in to change notification settings - Fork 86
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
Progress bar when only searching for one pipeline is confusing #609
Comments
+1. In the edge case you're describing, where we're only searching one pipeline, we could have the cmdline progress bar show 0% before the pipeline is fitted and 100% after. But I agree we could also simply omit the progress bar entirely when there's only one pipeline. |
Related to #245. From what I remember from my experimentation that there wasn't a perfect fix - each implementation resulted in some edge case being off. IIRC I couldn't fix this behavior (new line with new pipeline uses next percentage i.e only pipeline starts with 100%) as the alternative would be for the next pipeline to retain the same percentage which is confusing in another way (i.e first pipeline hits 50% and the next will keep 50% until finished). Might be worth brainstorming options other than TQDM. |
@jeremyliweishih agreed. I think we should move off TQDM. Will reorganize these tickets soon. For the moment let's hold off on working on TQDM-related issues. |
#761 will fix this, keeping it open until then |
To help me debug, I was running automl search with just one pipeline. When I look at the output, it makes feel as if the search is already complete since I see the 100%. Minor issue, but perhaps we can clean up the output
The text was updated successfully, but these errors were encountered: