-
Notifications
You must be signed in to change notification settings - Fork 31
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 #21
Comments
Noting here that this enhancement could be a step towards @jdagdelen's suggestion of built-in profiling: because |
Is there a way to do this automatically? I can see if |
Yeah, I was thinking of something along the lines of: self.total_items = 23432
for i in items:
yield i And it should build the appropriate tqdm progress bar. |
What do you want as a best practice? A |
It shouldn't matter which one and maggma should just work with it. If you
give it no total count it should still have progress bar that increments
and provides it/s. Basically this needs to be robust to bad and good user
builder code.
Thanks in advance,
Shyam Dwaraknath
Materials Research Scientist
Lawrence Berkeley National Laboratory
…On Tue, Apr 24, 2018 at 5:04 PM, Matthew Horton ***@***.***> wrote:
What do you want as a best practice? A yield, a cursor..?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQDC-sdxuzY5E-ZDipxPy48XMd-gBUXUks5tr72QgaJpZM4TZanY>
.
|
Right. If there's no count, it would still be valuable to see it/s. I think the runner can try to call |
Taken care of with #24 |
Is there anyway we could build in a global progress bar for builders that also worked well with logger/input outputs and didn't require complex logic?
The text was updated successfully, but these errors were encountered: