-
Notifications
You must be signed in to change notification settings - Fork 18
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 #28
Comments
An option that i'm aware of is tqdm. Any other ideas? |
I think I also see for example the library progress; but, (If need be we could also certainly write our own.) I think the biggest issue is that I'm not aware of libraries that control stdout in such a way that you can freely write to it without conflict with the progress bar. So, for example, Beyond that, we could get a simple integration out the door pretty easily, since the nprintML runner iterates over pipeline steps. An improvement could be integrating the progress bar more deeply, such that steps can produce smaller increments as they progress – this would be most useful (and easiest) within PCAP ingestion – but, that's not so immediately necessary. |
|
Sure – certainly for the time being, at least. (I'm not sure how we would
reach into AutoGluon either.)
…On Mon, Mar 15, 2021 at 8:07 AM Jordan Holland ***@***.***> wrote:
tqdm is probably our best bet as it can slot in to a process pool without
any code. I'm mostly convinced we just want a progress bar when we're
actually running nPrint (i.e. 5/500 files being processed) and not the
entire pipeline. We have no real access to the progress of AutoML beyond
its own output.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEBUNWVIVQBTVKQ567RKXTTDYBAXANCNFSM4UVQRBGA>
.
|
No description provided.
The text was updated successfully, but these errors were encountered: